1 |
On Sat, 2005-08-27 at 03:42 -0500, Brian Harring wrote: |
2 |
> Further, while no one has yet proposed anything concrete, people have |
3 |
> been after revamping the profile implementation. Quite likely if/when |
4 |
> this occurs, it's going to require a seperate directory to avoid any |
5 |
> issues with older portage installations accessing it. |
6 |
> Shifting the files now while changes are being made addresses that |
7 |
> concern, and makes things a bit more logical. |
8 |
|
9 |
This could still be done under profiles. Personally, I like the idea of |
10 |
something more like this: |
11 |
|
12 |
project/os/arch/version for profiles |
13 |
|
14 |
This would give us something like this: |
15 |
|
16 |
default/linux/x86/2006.0 |
17 |
default/freebsd/alpha/2006.0 |
18 |
hardened/linux/amd64/2006.0/2.4 |
19 |
hardened/freebsd/x86/2006.0 |
20 |
uclibc/linux/mips/2006.0/cobalt |
21 |
server/linux/x86/2006.0 |
22 |
|
23 |
etc. |
24 |
|
25 |
> Two scenarios for how this will result in visible issues for people- |
26 |
> 1) CVS users, aka, devs. Devs *should* be running latest portage, |
27 |
> which would know about the shift. If they're running an older |
28 |
> portage version and aren't willing to upgrade, they tag the |
29 |
> symlinks themselves. It's a minor annoyance frankly; assuming they |
30 |
> read -dev (like they're suppossed to :P ), they'll know in advance |
31 |
> it's coming. |
32 |
|
33 |
Many devs use the latest stable versions of packages rather than testing |
34 |
versions. I tend to find this to be a good thing as there are often |
35 |
bugs in particular combinations of package versions that aren't |
36 |
necessarily spotted when running all ~arch. |
37 |
|
38 |
Also, devs are not required to read or even be subscribed to -dev. |
39 |
|
40 |
-- |
41 |
Chris Gianelloni |
42 |
Release Engineering - Strategic Lead/QA Manager |
43 |
Games - Developer |
44 |
Gentoo Linux |