| 1 |
On Thu, 2005-01-06 at 11:00 -0800, David Bryson wrote: |
| 2 |
> Hi all, |
| 3 |
> Haven't seen any traffic on the list since I subscribed, so I thought I'd reach out and see if anyone was listening. |
| 4 |
> |
| 5 |
> I was playing around with cascading profiles recently, specifically packages.build, and I noticed that it cascades the same as all other files in profiles. |
| 6 |
> |
| 7 |
> However, it seemed to me that the way the build order was structured was odd. |
| 8 |
> If I have the following setup: |
| 9 |
> |
| 10 |
> /foo/packages.build = "sys-pretend/alice" |
| 11 |
> /foo/bar/packages.build = "sys-pretend/bob" |
| 12 |
> |
| 13 |
> (= is the contents of the file) |
| 14 |
> |
| 15 |
> The build order will be: |
| 16 |
> emerge bob |
| 17 |
> emerge alice |
| 18 |
> |
| 19 |
> It would seem as though the parent package.builds would be more likely to contain standard libraries and support packages, and the children package.builds would include slightly more specific packages that depended on the parent librariies. |
| 20 |
> |
| 21 |
> Thoughts on reversing the build order in catalyst for packages.build ? |
| 22 |
|
| 23 |
I think the reasoning behind this is that catalyst always processes |
| 24 |
profiles from right to left, just like portage does. I'm not really |
| 25 |
sure why it works like it does, so you won't find me changing it... ;] |
| 26 |
|
| 27 |
-- |
| 28 |
Chris Gianelloni |
| 29 |
Release Engineering - Operational/QA Manager |
| 30 |
Games - Developer |
| 31 |
Gentoo Linux |
Archives