From: Alistair Bush <ali_bush@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] QA within java overlays.
Date: Sun, 18 Jan 2009 22:47:28 +1300 [thread overview]
Message-ID: <4972FAB0.4020402@gentoo.org> (raw)
I have been looking at qa of the 2 java overlays (java-overlay and
java-experimental) and have noticed a few things
1) Running repoman ( and even qualidus, tho I still need to investigate
this more ) on java-experimental is a waste of time. Both assume only
that gentoo and java-experimental exist. This results in
a) the inability to find eclasses, aka, java-maven-*.eclass; and
b) the inability to find packages that are only located within java-overlay
I have had a short discussion with zmedico about added the concept of a
"parent" overlay so that repoman can find packages.
So far zmedico has suggested merging java-overlay and java-experimental.
2) QA within java-overlay is pretty poor.
eg.
KEYWORDS.stupid 5
dev-java/abbot/abbot-0.13.1-r1.ebuild
dev-java/byaccj/byaccj-1.14.ebuild
dev-java/gnu-crypto/gnu-crypto-2.1.0.ebuild
dev-java/jdic/jdic-0.9.1.ebuild (believe this may have been my
doing, certainly remember looking at this )
dev-java/libeds-java/libeds-java-0.5.1.ebuild
There also seem to be a lot of packages that have *DEPENDS on packages
within java-experimental, that are keyworded for arch's that don't have
a package also keyworded for that arch.
Now im going to start looking at all of these issues. But please ensure
you run repoman and correct any issues you find. I also believe that we
should always consider whether a change within the gentoo repo will have
effects on java-overlay. While java-overlay is ~arch by nature lets not
break it thru carelessness.
Alistair.
reply other threads:[~2009-01-18 9:47 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=4972FAB0.4020402@gentoo.org \
--to=ali_bush@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