1 |
Op maandag 24-11-2008 om 06:00 uur [tijdzone -0800], schreef Mark |
2 |
Knecht: |
3 |
> On Sun, Nov 23, 2008 at 10:26 PM, Duncan <1i5t5.duncan@×××.net> wrote: |
4 |
> > "Mark Knecht" <markknecht@×××××.com> posted |
5 |
> > 5bdc1c8b0811231435y2eea1b1by366c787c983c1089@××××××××××.com, excerpted |
6 |
> > below, on Sun, 23 Nov 2008 14:35:42 -0800: |
7 |
> > |
8 |
> >> The root cause of this is I wanted to emerge the newest version of |
9 |
> >> Ardour from the pro-audio overlay and ran into a new message about it |
10 |
> >> being masked by something called EAPI 2 which according to the message |
11 |
> >> requires a 'newer' version of portage. (No revision given.) That's all |
12 |
> >> this was about, and there's absoutely no rush to fix it as I'm not |
13 |
> >> likely to really use Ardour. Just wanted to take a look at what sort of |
14 |
> >> headway they are making with their feature set so it's really nothing |
15 |
> >> but pure curiosity. |
16 |
> > |
17 |
> > OK. FWIW, for EAPI-2, you need the new ~arch portage-2.2-rcX series. |
18 |
> > EAPI-2 is allowed in various overlays and now in ~arch, but not in stable |
19 |
> > until a stable portage supports it. It'll bring a number of new features |
20 |
> > including full set support, per-package use-defaults (previously a USE |
21 |
> > flag could be defaulted to on per profile, but not per package, off being |
22 |
> > the unset default, of course), and IIRC use dependencies (if a package |
23 |
> > requires say C++ support and gcc has been built without it, it must now |
24 |
> > die with an error message telling the user to make the change, with use- |
25 |
> > deps, it could force gcc to be recompiled with C++ instead of dying, thus |
26 |
> > avoiding somebody leaving a 200-package emerge going overnight, only to |
27 |
> > come back the next day to find out it stopped with package #2 due to a |
28 |
> > USE dependency death). |
29 |
> > |
30 |
> > So there are some nice things coming in EAPI-2 and a number of packages |
31 |
> > can really use them. But an EAPI-2 supporting portage, while now in the |
32 |
> > tree, remains unstable, as there are still a few bugs to work out before |
33 |
> > it goes fully stable. So if you prefer a stable portage, you'll have to |
34 |
> > wait for EAPI-2, and any packages requiring it (which by definition can't |
35 |
> > be stabilized until an EAPI-2 portage is stable too). |
36 |
> > |
37 |
> > -- |
38 |
> > Duncan - List replies preferred. No HTML msgs. |
39 |
> |
40 |
> Thanks Duncan. I basically understand the portage stuff, in the sense |
41 |
> that it's a new feature. I read a few eamils form the portage |
42 |
> developers, etc., and got a sense of some of what it is supposed to |
43 |
> do. that part I'm OK with, as I am, I guess, with the idea that |
44 |
> someone who wrote the Ardour ebuild is requiring these new features. |
45 |
> |
46 |
> My real question is what is required to build that portage on an |
47 |
> ~amd64 machine so that I can build Ardour? Is anyone on this list |
48 |
> using portage-2.2.x? If so how did they get it to build? |
49 |
> |
50 |
I run sys-apps/portage-2.2_rc15 |
51 |
But that just got installed with the updates. Not sure if there are |
52 |
special requirements or not. |
53 |
> Thanks, |
54 |
> Mark |
55 |
> |