| 1 |
Zac Medico schrieb: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> Ned Ludd wrote: |
| 6 |
>> How do you think we should handle it? |
| 7 |
>> Should we install a post_sync in a postinst phase outside of portage's |
| 8 |
>> handling if and only if not post_sync already exists? |
| 9 |
>> Should we change it to handled a postsync.d by default? |
| 10 |
>> Should we do both? I'm open as heck but would like to start to |
| 11 |
>> finalize then document it's behavior. I feel it could be one of the |
| 12 |
>> next untapped really useful features of portage. glsa-checking, news |
| 13 |
>> handling, search db updating, and stuff etc.. |
| 14 |
> |
| 15 |
> |
| 16 |
> Given the existing support for /etc/portage/bin/post_sync, the user has the freedom to do anything they want. If a program needs to make use of the post_sync trigger, it's documentation can simply state that a certain command needs the be run and the user can add that command to their post_sync script. Is that not easy and flexible enough? |
| 17 |
|
| 18 |
Well, it requires user intervention, pretty much the same argument as |
| 19 |
for any other foo.d change in any package (I don't have a personal |
| 20 |
preference here, though using bashrc for this definitely isn't a good idea). |
| 21 |
|
| 22 |
Marius |
| 23 |
-- |
| 24 |
gentoo-portage-dev@g.o mailing list |
Archives