Re: [gentoo-portage-dev] gentoolkit.git repository reorganized

[Brian Dolbec]

On Fri, 6 Nov 2015 18:35:54 -0500
Mike Gilbert <floppym@g.o> wrote:

> On Fri, Oct 30, 2015 at 1:39 AM, Michał Górny <mgorny@g.o>
> wrote:
> > On Thu, 29 Oct 2015 21:06:33 -0700
> > Brian Dolbec <dolsen@g.o> wrote:
> >
> >> On Thu, 29 Oct 2015 17:37:26 -0400
> >> Mike Frysinger <vapier@g.o> wrote:
> >>
> >> > On 22 Oct 2015 12:54, Paul Varner wrote:
> >> > > Mike, I know you're busy with other stuff, but if you ever
> >> > > want to see a new gentoolkit/gentoolkit-dev release, consider
> >> > > this your authorization to just do it.  The README.dev files
> >> > > state how to make releases.
> >> >
> >> > thanks, i think this will help a lot
> >> >
> >> > > Since, the tools have dwindled down in gentoolkit-dev, I do
> >> > > think it does make sense to keep it in the same repo and merge
> >> > > the packages together behind a USE flag.  I will revert the
> >> > > commit, that emptied the genttolkit-dev branch and ask mgorny
> >> > > to nuke the new gentoolkit-dev repository.
> >> > >
> >> > > As I get time, I will work towards moving the gentoolkit-dev
> >> > > tools into gentoolkit and putting them behind a USE flag in
> >> > > the ebuild.
> >> >
> >> > i'm no distutils expert, and every time i try to do something
> >> > "fancy", i get frustrated by the module :).  do people know of
> >> > examples where you can do optional installs with a flag ?  a
> >> > cookbook sort of entry here would help and i could take care of
> >> > merging in say ekeyword. -mike
> >>
> >> Have a look at layman's setup.py.  It parses IUSE to set the
> >> installed files via setup.py.  It may not be the best method, but
> >> it does work.
> >>
> >> The layman ebuild sets deps acording to the ISUE flags and setup.py
> >> sets the installed modules on the python side.
> >
> > Sorry, what?! That's a huge QA violation. There is *NO* guarantee
> > that USE will be exported. In fact, it is only exported because of
> > poor design inside Portage that could result in the variable
> > getting lost otherwise.
>
> PMS says that USE will be exported to the environment. So, this should
> not break with any PMS-compliant package manager.
>
> Personally, it makes me cringe, but I suppose it doesn't make a lot of
> sense to invent an entirely new envvar for it.
>

I remember discussing this with you at the time.  setup.py is capable
of taking args for this, but the distutils eclass and or distutils
itself was not capable of doing that from an ebuild.  So, this was my
only option at the time.  If that has changed, it'll be news to me :)


Make it capable to pass options like automake and I'll be glad to change
it.
 

-- 
Brian Dolbec <dolsen>