1 |
On Thu, August 22, 2013 11:07, Neil Bothwick wrote: |
2 |
> On Thu, 22 Aug 2013 10:23:57 +0200, J. Roeleveld wrote: |
3 |
> |
4 |
>> True, but with the scripts that are floating in this thread, a usable |
5 |
>> solution can be build. |
6 |
> |
7 |
> It took me a few seconds to do that, so why hasn't it been done before? |
8 |
> It's obviously not due to the work involved, so it must be that no one |
9 |
> involved believes there is a need for it, an belief I share. |
10 |
> |
11 |
>> Only need to finalize that into a generic option and document it in the |
12 |
>> wiki. Preferably as a "post-emerge" command. |
13 |
> |
14 |
> No thanks you. As Alan said, portage doesn't have a mechanism to run a |
15 |
> command after a batch emerge, it would have to be done after every single |
16 |
> package. So the next time a bunch of Perl packages and their virtuals are |
17 |
> updated, look forward to it being run fifty times. |
18 |
|
19 |
I would not want it run fifty times. I would prefer if there was a way to |
20 |
have a script run automagically when emerge finished with a batch-update. |
21 |
|
22 |
That script is a usefull addition to the set of commands I use when |
23 |
updating the server. It would help me to avoid rebuilding the initramfs |
24 |
each time I do an update. |
25 |
|
26 |
-- |
27 |
Joost |