| 1 |
> Try the -dev list for the MANPATH thing. |
| 2 |
|
| 3 |
Shall do that. |
| 4 |
|
| 5 |
> I think "cron" might be a better global USE flag than "sqlite". Users |
| 6 |
> will think "oh, of course I want the apropos/whatis database to be |
| 7 |
> updated nightly" with USE=cron. Unless they happen to know that those |
| 8 |
> databases are implemented in sqlite, they'll probably just guess at the |
| 9 |
> meaning of USE=sqlite. |
| 10 |
|
| 11 |
Good point. I have the USE description in metadata.xml, but even there |
| 12 |
did not comment that cron scripts would be installed. Not sure whether |
| 13 |
to call it cron, because users would assume it would only install the |
| 14 |
cron script and not need sqlite for database generation. |
| 15 |
|
| 16 |
> I would also suggest dropping the "+" defaults unless doing so severely |
| 17 |
> cripples the package. The whole point of USE flags is that I can set |
| 18 |
> them and all ebuilds will use them -- that stops working if developers |
| 19 |
> make their own preferences default in ebuilds. |
| 20 |
|
| 21 |
I thought about dropping the default for sqlite, and will probably do |
| 22 |
so. As for manpager: it has + even in man-db, so I thought it would be |
| 23 |
best to keep that consistent. |
| 24 |
|
| 25 |
> [snip] |
| 26 |
> This might be more appropriate in pkg_config(), because it modifies a |
| 27 |
> file that doesn't belong to the package manager, namely mandoc.db. That |
| 28 |
> could also solve your MANPATH issue by dumb luck; I'm not sure what the |
| 29 |
> environment will look like during emerge --config. |
| 30 |
|
| 31 |
I will try that out, thanks very much for the suggestions/fixes. |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573 |
Archives