| 1 |
On Thu, 2004-04-01 at 15:59, Pieter Van den Abeele wrote: |
| 2 |
> On 01 Apr 2004, at 22:52, John Davis wrote: |
| 3 |
> |
| 4 |
> > profile: default-x86-2004.0 #for non-stackable profiles |
| 5 |
> > profile: default-linux/x86/2004.0 #for stackable profiles |
| 6 |
> |
| 7 |
> Not sure that I have the absolute latest cvs sources, but |
| 8 |
> |
| 9 |
> with default-ppc-2004.0 set as profile, stages are put in the default |
| 10 |
> directory, rather than in the default-ppc-2004.0 directory. |
| 11 |
> |
| 12 |
> Pieter Van den Abeele |
| 13 |
> |
| 14 |
> |
| 15 |
> -- |
| 16 |
> gentoo-releng@g.o mailing list |
| 17 |
|
| 18 |
I knew that I forgot to mention something :) |
| 19 |
|
| 20 |
This behaviour is expected. The reason that all build stuffs go into a |
| 21 |
directory named for rel_type rather than profile is a fix for stackable |
| 22 |
profiles. |
| 23 |
|
| 24 |
Say that I have a stackable profile specified as "profile: |
| 25 |
default-linux/x86/2004.0" in my spec file. If the old catalyst storage |
| 26 |
naming convention was used (/var/tmp/catalyst/builds/$target_profile), |
| 27 |
my stackable profile (whose value is in target_profile) would muck the |
| 28 |
entire situation up by redoing the naming scheme to |
| 29 |
/var/tmp/catalyst/builds/default-linux/x86/2004.0/. |
| 30 |
|
| 31 |
The behaviour is the same (one top-level profile-specific directory), |
| 32 |
but the naming a touch different. |
| 33 |
|
| 34 |
Cheers, |
| 35 |
//zhen |
| 36 |
-- |
| 37 |
John Davis |
| 38 |
Gentoo Linux Developer |
| 39 |
<http://dev.gentoo.org/~zhen> |
| 40 |
|
| 41 |
---- |
| 42 |
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc> |
| 43 |
Fingerprint: 2364 71BD 4BC2 705D F338 FF70 6650 1235 1946 2D47 |
Archives