| 1 |
On Sun, 24 Apr 2011 16:58:23 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> I feel that the current approach (using INSTALL_MASK) to control |
| 5 |
> whether these configuration files are installed or not is not well |
| 6 |
> documented. We tell people about it on the mailing lists, but I do |
| 7 |
> not know of a place where it is documented. |
| 8 |
> |
| 9 |
> Also, it seems to be an all or nothing arrangement. If I do not want |
| 10 |
> logrotate support, I have to set the INSTALL_MASK then if I decide |
| 11 |
> later I want it, I have to unset the INSTALL_MASK and run "emerge -e |
| 12 |
> world" to get the files installed. |
| 13 |
|
| 14 |
I'm currently working on improving the situation. I'd like to create |
| 15 |
a tool which would allow users to easily add and remove INSTALL_MASKs |
| 16 |
(including a few common sets), and rebuild the packages as necessary. |
| 17 |
This, however, would require some fixes in portage [1]. |
| 18 |
|
| 19 |
> I guess the argument against the use flag was that packages were being |
| 20 |
> rebuilt just to install configuration files. I can see how that could |
| 21 |
> be a pita for big packages. Did anyone ever bring up using pkg_config |
| 22 |
> to un/install these files based on the use flags? |
| 23 |
|
| 24 |
I don't think that would work. And if it does, then either PM or even |
| 25 |
PMS is broken by design. The pkg_config() phase should have the same |
| 26 |
flags set as the build had, or don't refer to flags at all. |
| 27 |
|
| 28 |
In addition, upstream-installed config files often require running sed. |
| 29 |
And this requires unpacking & configuring the package. Really don't |
| 30 |
seem appropriate for pkg_config(). |
| 31 |
|
| 32 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=364633 |
| 33 |
|
| 34 |
-- |
| 35 |
Best regards, |
| 36 |
Michał Górny |
Archives