On Thu, Dec 04, 2008 at 09:08:53AM +0200, Penguin Lover Alan McKinnon squawked:
> The answer is not in the ebuild, it's in the eclass. You will find it at
> $PORTDIR/ecalss/enlightenment.eclass. I'll take you through the relevant bits
> step by step. Lines 34 to 58 are the relevant ones, and everything afterwards
> depends on the value assigned to E_STATE. I'll assume you are familiar with
> bash's parameter expansion syntax (man bash, line 1135 if not)
>
> E_STATE="release"
> if [[ ${PV/9999} != ${PV} ]] ; then
> E_STATE="live"
> elif [[ -n ${E_SNAP_DATE} ]] ; then
> E_STATE="snap"
> else
> E_STATE="release"
> fi
D'oh. My earlier snip was also from the same eclass. For some reason I
just didn't look hard enough to see if those variables were defined in
the same file. Thanks!
> > In other words, is it hardcoded somethere in portage that all 9999
> > version numbers automatically trigger that variable above to be live?
> > Or is there some configuration somewhere?
>
> It's a convention. No sane coder will ever release a package with version
> 9999, that is conventionally used by devs for their development stuff in
> cvs/svn/git/whatever, so vapier is just falling in line.
Not exactly what I meant. But your answer above already solve the
problem: in my opinion it is one thing to "fall in line" for each
package (in this case, enlightenment) separately, and a completely
different thing to just make the assumption that 9999 version numbers
will never be used (practical experience aside, of course :) ).
> so you could simply emerge a specific version and as long as your keywords
> were correct in portage.keywords, the right thing would happen.
Okay, so since I run a mostly ~x86 system, I can just keyword mask e17
if I don't want those packages.
I will probably just suck it up and install e17 anyway: I use DR16 on
my stable desktop, but mostly fvwm on my testing laptop. I tried DR17
a bit back on my laptop, but way back then something in the chain of
DR17-Xorg-my ATI video card doesn't like the eye candy. I'll give it
another try to see if it has miraculously gotten better. (Though I am
rather fond of my fvwm setup now; I just wish I can figure out a way
to get transparencies to play nice with some of the quirky stuff I
have in my configs.)
> I recommend you do what I did - read the eclass and all the ebuilds, plus man
> 5 ebuild, plus a long wiki document I found on the dev section at gentoo.org
> written by Ciaran McCreesh.
I've read man 5 ebuild and the HOWTO on the gentoo.org page. Haven't
seen Ciaran's wiki document yet. I think (if I have some time) I
should take your advice and just read the eclass and the ebuilds. I
read about ebuilds when I was trying to write a ebuild myself--3 days
into the effort, something still wasn't working, and someone else beat
me by putting one into sunrise. C'est la vie.
Thanks
W
PS, I'll give e17 another look. Perhaps I'll take you up on your offer
for the overlay.
--
I couldn't repair your brakes, so I made your horn louder.
Sortir en Pantoufles: up 727 days, 13:15
