| 1 |
On Thursday 01 February 2007 18:48, Mike Frysinger wrote: |
| 2 |
> On Thursday 01 February 2007, Daniel Black wrote: |
| 3 |
> > Also creates the following symlinks to it |
| 4 |
> |
| 5 |
> i dont see much value in these symlinks ... what do they gain us ? |
| 6 |
> |
| 7 |
|
| 8 |
An easy way to find the closest config when merging a revision/version bump of |
| 9 |
the same package. There are probably some cleaner ways with portage foo. |
| 10 |
|
| 11 |
I see your point that it is a weak reason for symlinks to exist. The hard work |
| 12 |
should be done by the eclass to find the closest config. |
| 13 |
|
| 14 |
> > As some packages, like uclibc, have regular cross compile functionality |
| 15 |
> > which require separate config files for each host. This can be achieved |
| 16 |
> > with the -s option. |
| 17 |
> |
| 18 |
> i dont think the ebuild should care whether it's being cross-compiled ... |
| 19 |
> any package should be cross-compilable so the ebuild should really be |
| 20 |
> agnostic |
| 21 |
> |
| 22 |
> in other words, the search path for the .config should always check |
| 23 |
> $CTARGET subdirs followed by $CHOST followed by the normal $CATEGORY |
| 24 |
|
| 25 |
Sure, makes sense. |
| 26 |
|
| 27 |
So clarifying by default the save_config will store it in normal $CATEGORY and |
| 28 |
allow the user to move it into under specific $CTARGET or $CHOST directory if |
| 29 |
that is their desire. |
| 30 |
|
| 31 |
> -mike |
| 32 |
|
| 33 |
-- |
| 34 |
Daniel Black <dragonheart@g.o> |
| 35 |
Gentoo Foundation |
Archives