From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Cc: axxo@gentoo.org
Subject: Re: [gentoo-java] overlays moving to overlays.gentoo.org
Date: Tue, 18 Jul 2006 09:43:23 -0400 [thread overview]
Message-ID: <44BCE57B.2070807@gentoo.org> (raw)
In-Reply-To: <20060717233526.GA29405@acissej.telenet.be>
Thomas Matthijs wrote:
> fyi,
> There is alot of work hidden in there. If you plan to re-port every
> ebuild, you'll be duplicating alot of annoying work
>
You're right of course. If there haven't been any changes for a package
aside from keywords since the overlay was sync'd, I generally just yank
the ebuild, rebump it, and make sure it's using the new eclasses.
iirc, it was mostly packages that didn't use ant that needed a lot of
work. In particular, I recall db being a pain. Does that sound about right?
- Josh
--
gentoo-java@gentoo.org mailing list
prev parent reply other threads:[~2006-07-18 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 18:53 [gentoo-java] overlays moving to overlays.gentoo.org Joshua Nichols
2006-07-17 21:02 ` Joshua Nichols
2006-07-17 21:29 ` Ivan Yosifov
2006-07-17 22:05 ` Joshua Nichols
2006-07-17 22:16 ` Krzysiek Pawlik
2006-07-17 23:02 ` Joshua Nichols
2006-07-17 23:35 ` Thomas Matthijs
2006-07-18 13:43 ` Joshua Nichols [this message]
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=44BCE57B.2070807@gentoo.org \
--to=nichoj@gentoo.org \
--cc=axxo@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