From: "Ernst de Haan" <wfe.dehaan@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Old submitted ebuilds that depended on axxo-overlay (dev-java/xmlenc, dev-java/xins)
Date: Wed, 19 Jul 2006 21:58:31 +0200 [thread overview]
Message-ID: <fa47cf900607191258n14ca93d8l75cb20b37ea1d32d@mail.gmail.com> (raw)
Ages ago I submitted some ebuilds. One for "xmlenc" and one for
"XINS". Both under dev-java. At the time, these ebuilds had to go into
gentoo-experimental, because the new Java platform was to be merged
into the main tree.
Now that new Java system is in the main tree, what should I do with the ebuilds?
Note that the xmlenc ebuild is still up-to-date. The XINS ebuild I
will need to update. The stable version moved from 1.3.0 to 1.4.2.
See:
http://gentooexperimental.org/svn/java/gentoo-java-experimental/dev-java/xmlenc/
http://gentooexperimental.org/svn/java/gentoo-java-experimental/dev-java/xins/
http://bugs.gentoo.org/show_bug.cgi?id=116489
http://bugs.gentoo.org/show_bug.cgi?id=116876
Regards,
Ernst
--
gentoo-java@gentoo.org mailing list
reply other threads:[~2006-07-19 19:59 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=fa47cf900607191258n14ca93d8l75cb20b37ea1d32d@mail.gmail.com \
--to=wfe.dehaan@gmail.com \
--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