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