public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] dev-java/xerces-2.6* slotmove
Date: Fri, 01 Dec 2006 00:26:40 +0100	[thread overview]
Message-ID: <456F68B0.60701@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

today I've made a new revbump of xerces-2.6.2 which changes SLOT to 2.6.
Following the same scenario that led to slotting of xerces-2.3. That
means if (and only if) your package builds/runs fine with xerces 2.6.x
but breaks with any higher version, you should depend on =xerces-2.6*
and call java-pkg_jar-from xerces-2.6 (similarly with other eclass
functions). SLOT 2 xerces now contains versions >=2.7.* and should be
used with packages that don't break on the internal changes there (which
is the most luckily :) in that case you should depend on >=xerces-2.7
(to pull the right slot) and use 'xerces-2' with eclass functions as
usual. This will get much easier when slot-based dependencies are
available for general use (in stable portage with EAPI bump).
All relevant dependencies in portage tree and our overlays were updated
accordingly, with the exception of jboss stuff in migrated-overlay which
should be taken care of by our minions (as it was one of their package
that actually led to this slotmove :)
If we find something that breaks with 2.8 but works with 2.7, this will
be repeated for 2.7 slotmove (I hope not so soon :)

Regards,
- --
Vlastimil Babka (Caster)
Gentoo/Java
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFb2iutbrAj05h3oQRAjmoAJ9oVsV56bwHiirwwSZyiEkJJwHq1ACdG6E1
osCShc447mtiWSHsBy180yg=
=j2Oa
-----END PGP SIGNATURE-----
-- 
gentoo-java@gentoo.org mailing list



                 reply	other threads:[~2006-11-30 23:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=456F68B0.60701@gentoo.org \
    --to=caster@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