From: "Wiktor Wandachowicz" <siryes@gmail.com>
To: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] Furball
Date: Sat, 24 Jun 2006 12:03:34 +0200 [thread overview]
Message-ID: <254054bc0606240303h74d40f30m350453ac88166d10@mail.gmail.com> (raw)
In-Reply-To: <1151125056.11154.11.camel@procyon.operationaldynamics.com>
2006/6/24, Andrew Cowie <andrew@operationaldynamics.com>:
> Given the furball that is erupting on gentoo-dev, I think that you need
> to make a very decisive point and make it quickly. I therefore recommend
> that you go ahead and merge all the migration packages to the official
> portage tree *now*.
>
> If manual action is necessary during the upgrade process, well, that's
> certainly nothing people are unprepared to encounter. This is Gentoo
> after all.
>
> Now that I think of it, this is, after all, "release early, release
> often". So pull the trigger, baby: freeze over, merge to HEAD.
In one word: YES!
That would finaly bring the scale effect to the long-awaited change
of handling Java in Gentoo. More apt users willing to check -> more
bug reports -> more work resolwing them (on a short term) -> but
finally: a quicker adoption.
Having a separate overlay is a very clean and trouble-free approach.
However, it requires extra work to be used (not *that* much, but still)
and excludes a large number of Gentoo and Java users that could
otherwise help killing silly bugs rather quickly.
I'd love to report officially in b.g.o should any trouble arise from using
the ~arch generation-2 Java packages. Probably with solution(s)!
Cheers,
Wiktor
--
Registered Linux user #390131 (http://counter.li.org)
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-24 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 4:57 [gentoo-java] Furball Andrew Cowie
2006-06-24 10:03 ` Wiktor Wandachowicz [this message]
2006-06-24 12:01 ` Ivan Yosifov
2006-06-24 18:07 ` Joshua Nichols
2006-06-24 18:50 ` Joshua Nichols
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=254054bc0606240303h74d40f30m350453ac88166d10@mail.gmail.com \
--to=siryes@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