Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-java
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-java@g.o
From: Alistair Bush <ali_bush@g.o>
Subject: Re: QA: java-experimental
Date: Mon, 02 Feb 2009 07:33:45 +1300
Krzysztof Pawlik wrote:
> Alistair Bush wrote:
> So.. maybe it's time to re-think the way java-* overlays are used? I'd opt for
> "staging" approach: let java-experimental be well, experimental - you don't know
> whenever something will work, is a good idea, you're still working on it, etc.
> java-overlay would become a staging ground: after some time (to be defined)
> ebuilds would end in main tree.
> 
> So the ebuild migration would look like:
>  * experimental: fresh stuff
>  * overlay: checked by somebody else (peer reviewed)
>  * main tree: after some time in overlay (like a month)
> 
> That would enforce from where one can have dependencies in particular overlay,
> would (hopefully) reduce the size of overlays.

Yes that would be good.  Half the problem is that java-overlay became a
huge playground of experimental packages.  Just look at all the maven
packages.  Ive never been able to get maven to work from java-overlay
and had to hack and slash my way thru them to get them to install in the
first place.  My guess is that everyone is guilty of this in some way.
(I known I am).  Whether it is packages that did work but now don't to
the ones that never worked in the first place it doesn't matter.  From
what I understand java-overlay was meant to help reduce the amount of
maintenance we had to do within the gentoo tree.  It has been very
successful at that,  now we just have overlays full.....

Here are also things ppl should think about. and implement.

1) If you bump a package, with more than trivial changes (aka you don't
finish making them, removing bundled jars, etc, etc) commit it to
java-experimental, never java-overlay.  I don't care what keywords you
give it, if it ain't ready it ain't java-overlay.

2) If you delete (even an outdated ebuild) ensure that there are no
reverse dependencies.  If you are deleting from java-overlay ensure
there are no reverse dependencies within java-overlay and
java-experimental.  (this seems to have occurred a bit.  packages
depending on =dev-java/package-1.1.1.  only to have 1.1.1 replaced by
1.1.2).

I could run on but i've run out of time.

> 
> Something similar was done:
> http://overlays.gentoo.org/proj/java/wiki/March_2007_Summary#Changesinoverlays
> 


References:
QA: java-experimental
-- Alistair Bush
Re: QA: java-experimental
-- Krzysztof Pawlik
Re: QA: java-experimental
-- Alistair Bush
Re: QA: java-experimental
-- Krzysztof Pawlik
Navigation:
Lists: gentoo-java: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: QA: java-experimental
Next by thread:
Meeting reminder
Previous by date:
Re: QA: java-experimental
Next by date:
Meeting reminder


Updated Jun 17, 2009

Summary: Archive of the gentoo-java mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.