Re: [gentoo-java] Java installation handling not acceptable

[Joshua Nichols]

Wiktor Wandachowicz wrote:

> > The transition period will end eventually. But you're right that the
> > new-style Java installation requires manual intervention Right Now (TM).
> > This is expected with many other packages that are in testing as well.
> > Problem is, Java is a requirement for many people and the (minor, IMHO)
> > hurdles just makes them unnecessarily angry. If one has to use testing
> > versions of packages, one also has to learn how to deal with them
> > correctly:
> > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3
> >
>
If you're upgrading an existing install or using stable keywords on a
new install, yes, there's some manual intervention required... But for
the record, if you're using testing keywords on a new install... it Just
Works (TM). I just did a fresh install over the weekend and was pleased
to see how well it went  :-D 

> > For the time being, one could write a script that could install testing
> > (~arch) Java on a stable profile - adding proper atoms to package.unmask
> > and package.keywords, checking the sanity, etc. But this work would
> > be outdated too some time in the future. It's just a matter of time when
> > these Java packages (and there are about 400 of them in portage!) will
> > become stabilized. The more time developers spend on this goal the
> > faster it becomes reality. And they don't get paid for it, remember.
> >
>
I was actually working on a script based on nelchael's find-unported.py
script, that would find all the packages using that have been migrated,
so it'd basically give you a list of things to put in
/etc/portage/package.keywords.

Also just had a revelation... could use that in combination with
find-unported.py to package.mask everything that was unported. This
would have the benefit of making it pretty obvious what stuff in a
dependency tree still needs to be migrated.

-- 
gentoo-java@g.o mailing list