1 |
On 2011-1-24 8:30 AM, "Jeremy Olexa" <darkside@g.o> wrote: |
2 |
|
3 |
> On Sat, 15 Jan 2011 05:35:10 -0500, Christopher Warrington wrote: |
4 |
>> On 2011-1-15 2:05 AM, "Alan Hourihane" <alanh@×××××××××××.uk> wrote: |
5 |
>>> Is there a way to run a script after an emerge --sync operation ? |
6 |
>> |
7 |
>> If you merge app-portage/portage-utils, you are supposed to be able |
8 |
>>to place scripts in ROOT/etc/portage/postsync.d/ that will get run. |
9 |
>> |
10 |
>> However, the script that I have in my ROOT/etc/portage/bin/post_sync |
11 |
>> has a hardcoded "/etc/portage/postsync.d/" instead of one based on my |
12 |
>>root. |
13 |
>> It looks like we'll have to fix that. I manually edited the post_sync |
14 |
>>script to point it to the proper ROOTed location, and the scripts ran |
15 |
>>after |
16 |
>>my most recent sync. |
17 |
> Fixed without a revbump - you'll need to remerge it. Sorry about the |
18 |
> trouble. :) |
19 |
|
20 |
Works for me. Thanks! |
21 |
|
22 |
However, I wonder if there's a quoting problem in the expansion. Shouldn't |
23 |
for f in "@GENTOO_PORTAGE_EPREFIX@"/etc/portage/postsync.d/* ; do |
24 |
be |
25 |
for f in "@GENTOO_PORTAGE_EPREFIX@/etc/portage/postsync.d/*" ; do |
26 |
? |
27 |
|
28 |
For example, on my machine, this expands to |
29 |
for f in "/Gentoo"/etc/portage/postsync.d/* ; do |
30 |
which works for me, but doesn't "look" right. |
31 |
|
32 |
-- |
33 |
Christopher Warrington <chris@×××××.net> |