Mailing List Archive

[PREFIX] More prefixed ebuilds
Hi guys,



I've been working with Matt and I've got some additional ebuilds that I
updated to work in prefixed environment - gentoolkit, gcc-config, some
others. Also, I created a baselayout that is better fit for a prefixed
environment (though there are still things to fix to work completely).
What's the proper place or method for getting these changes in?



Thanks

- Chris
Re: [PREFIX] More prefixed ebuilds [ In reply to ]
On Apr 24, 2006, at 4:20 PM, Christopher Chan wrote:
> Hi guys,
>
>
HI!

> I’ve been working with Matt and I’ve got some additional ebuilds
> that I updated to work in prefixed environment – gentoolkit, gcc-
> config, some others. Also, I created a baselayout that is better
> fit for a prefixed environment (though there are still things to
> fix to work completely). What’s the proper place or method for
> getting these changes in?
>
>

I'm gone for about 2 more weeks, but when I get back I will have anon
svn and a separate svn repo that I can give out accounts for. Oh, and
trac too.


--Kito





--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] More prefixed ebuilds [ In reply to ]
That sounds good Kito. I don't know if it had been discussed before, but I
was thinking it might be a good idea to create a prefix.eclass that can
share a set of functions. One function I was thinking of was to prepend the
EPREFIX, and have a smart enough to not add it if it already existed. It
seems like much of the work is figuring out where to add and where not to
add. It could give some sort of warning if the prefix was already there so
we know about it, yet does not break to build.



Thoughts on this idea?



- Chris
Re: [PREFIX] More prefixed ebuilds [ In reply to ]
On 24-04-2006 22:20:26 -0700, Christopher Chan wrote:
> That sounds good Kito. I don't know if it had been discussed before, but I
> was thinking it might be a good idea to create a prefix.eclass that can
> share a set of functions. One function I was thinking of was to prepend the
> EPREFIX, and have a smart enough to not add it if it already existed. It
> seems like much of the work is figuring out where to add and where not to
> add. It could give some sort of warning if the prefix was already there so
> we know about it, yet does not break to build.

Maybe you can make the first version of $(prefix [package]) function in
that case. It should return the prefix that was used when installing
package, or when no package given, the default prefix, so it can be used
also in --with-xxxxx=$(prefix xxxxxx)/usr/bin/xxxxxx or something.

There has been some discussions on this issue on this list before. Not
sure if I reword the idea correctly.


--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list