public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: Gentoo Java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Deprecating JDK 1.4
Date: Wed, 16 Jul 2008 20:38:39 +0300	[thread overview]
Message-ID: <487E321F.4050209@gentoo.org> (raw)
In-Reply-To: <4879D262.1080903@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]

Krzysiek Pawlik kirjoitti:
> 
> Hi,
> 
> As I mentioned in the thread "[gentoo-java] caucho-services, burlap and 
> hessian mess" I'm going to deprecate 1.4 - there was not much feedback 
> on that topic ;)
> 
> Current plan is:
> 
>  * migrate 5 remaining packages to generation 2 (or if masked remove 
> them) - current list (as of today): 
> http://dev.gentoo.org/~nelchael/java-generation-2/not-migrated-20080713

Yes that is the right place to start.

>  * make generation 1 eclasses die instead of QA violation warning

Agreed.

>  * change eclasses that have >?=virtual/jdk-1.4.* (java-gnome and 
> php4_4-sapi)

java-gnome eclass is not used by anything so just best to make that one 
die and you will want to check with the php people if that eclass is 
needed any more either

>  * rev bump every package with >?=virtual/jdk-1.4.*:
>    * if package has soft dependency on 1.4 (>=1.4) - raise it to 1.4 - 
> that's the easy case
>    * if package has hard dependency on 1.4 (=1.4) - try to compile with 
> 1.5, eventually patch it to work
>    * if package refuses to compile/work with >1.4 - package.mask, slate 
> for removal

Yeah just check for reverse deps.

>  * get all rev bumped packages stabilized (if package has stable version 
> in corresponding SLOT)
>  * remove old versions of touched packages
>  * remove java5 use flag
>  * start dropping generation 1 from the tree:
>    * make old eclasses a stub - so unmerge works

I would just leave a dying version because of all the ebuilds around.

>    * remove generation 1 bits from JDK ebuilds
>    * package.mask java-config-1*
>  * remove virtual/jdk-1.4.1

There's also a couple of other things to do with our tools so please 
talk with me before doing this step.

> 
> I'm also asking everybody for help: when the process starts please start 
> fixing ebuilds too - changing 370 packages is not an easy task to take 
> alone.
> 

I don't see why you would need to change this many packages.

Regards,
Petteri



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2008-07-16 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13 10:01 [gentoo-java] Deprecating JDK 1.4 Krzysiek Pawlik
     [not found] ` <d61c57300807130324o5446afaah3b94e23ada11e8ce@mail.gmail.com>
2008-07-13 10:31   ` [gentoo-java] " Krzysiek Pawlik
2008-07-14 21:16 ` Jörg Schaible
2008-07-16 12:15   ` Krzysiek Pawlik
2008-07-16 17:33     ` Petteri Räty
2008-07-16 17:57       ` Krzysiek Pawlik
2008-07-17 19:50     ` [gentoo-java] " Jörg Schaible
2008-07-19 17:06       ` Petteri Räty
2008-07-16 17:38 ` Petteri Räty [this message]
2008-07-16 17:59   ` [gentoo-java] " Krzysiek Pawlik
2008-07-16 18:09     ` Petteri Räty
2009-03-26 18:41       ` Serkan Kaba
2009-03-30 18:16         ` Petteri Räty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=487E321F.4050209@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-java@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox