On Wed, Aug 19, 2015 at 11:09:07AM -0400, cov...@ccs.covici.com wrote:
> Jc García <jyo.gar...@gmail.com> wrote:
>
> > 2015-08-18 10:38 GMT-06:00 <cov...@ccs.covici.com>:
> > > So, how do I get the -9999
> > > versions of the ebuilds to give me all the correct files like the 2.16.x
> > > versions do? I know the -9999 are from git, but it should do what
> > > gentoo wants.
> > This isn't realistic, you can't ask the devs to check every commit
> > upstream makes, exactly when it makes it, so they could update the
> > ebuild, if a 9999 ebuild isn't working try to fix it, Obviously
> > somthing changed with the dependecies, maybe versions, considering
> > gnome 3.18 is around the corner. Why do you think none of the 9999
> > ebuilds are keyworded? because they're not officially maintained for
> > any arch. My advice is wait if you don't want to mess with the
> > ebuilds, other wise, open up an editor and start making things work
> > for you, a good start would be to check all the autotools files for
> > changes in dependencies.
>
> Well, I would be willing to do that, but the only difference between the
> .999 ones and the regular ones is that the .9999 ones inherit virtualx
> and they have the following
> inherit eutils gnome2 multilib-minimal virtualx
> if [[ ${PV} = 9999 ]]; then
> inherit gnome2-live
> fi
>
> So, can you give me any guidance as to why multilib is not being
> honored?
>
The ebuild needs to contain all the steps required to build the
software. The build process for these particular pieces of software may
have changed enough that the -9999 ebuild does not contain all the steps
anymore.
As Jc Garcia said earlier:
> > Obviously somthing changed with the dependecies, maybe versions,
> > considering gnome 3.18 is around the corner.
Alec
