From: Thomas de Grenier de Latour <degrenier@easyconnect.fr>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Breaking up the beast known as app-games
Date: Sat, 6 Sep 2003 03:50:00 +0200 [thread overview]
Message-ID: <20030906035000.17fcce74.degrenier@easyconnect.fr> (raw)
In-Reply-To: <200309060017.43415.luke-jr@gentoo.org>
Just to make it clear, I also think a tree reorganisation is needed and
there has been some good ideas here (my preference goes to the flat
repository with multiple informative categories inside ebuilds, as
proposed by Jean Jordaan). My point is only that this is something that
has to be thought early enough to avoid forgeting any user when it
comes real.
On Sat, 6 Sep 2003 00:17:29 +0000
Luke-Jr <luke-jr@gentoo.org> wrote:
> Would it be possible to require a real user to run the 'emerge world'
> and say "yes" to a question?
If "emerge world" still works after the tree reorganisation, then there
is no backward compatibility issue. But it doesn't seem so obvious to
me: with many of the solution suggested so far, a current portage would
not even pass the dep caching that comes after the sync.
> If stdin cannot be opened (cron job), send root@localhost a mail.
Doesn't change the fact that the best a current version portage can do
is to inform you that a new version is available. If I do my next sync
in six month in my 486 gateway because of a new openssh bug, I shouldn't
be blocked only because I've ignored this information.
> Having two trees would require every package change to be done on each
> tree... Just as complex, I'd think.
There would be no need to maintain the old tree, but only to keep
something that is enough for people to make the transition (at least
new portage and his deps). This plus a mechanism to force portage
upgrade when really needed would be enough.
--
TGL.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-06 1:43 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 16:51 [gentoo-dev] Breaking up the beast known as app-games Mike Frysinger
2003-09-04 17:59 ` [gentoo-dev] Re: [gentoo-core] " Donny Davies
2003-09-04 18:07 ` Camille Huot
2003-09-04 19:02 ` Mike Frysinger
2003-09-04 19:45 ` Camille Huot
2003-09-04 20:14 ` Thomas de Grenier de Latour
2003-09-05 4:13 ` Mike Frysinger
2003-09-05 6:52 ` Thomas de Grenier de Latour
2003-09-05 8:15 ` Philippe Lafoucrière
2003-09-05 18:39 ` Thomas de Grenier de Latour
2003-09-06 0:17 ` Luke-Jr
2003-09-06 1:04 ` Mike Frysinger
2003-09-06 1:50 ` Thomas de Grenier de Latour [this message]
2003-09-06 2:03 ` Luke-Jr
2003-09-06 3:27 ` Robin H. Johnson
2003-09-06 4:18 ` Luke-Jr
2003-09-06 7:47 ` George Shapovalov
2003-09-06 13:38 ` Luke-Jr
2003-09-06 15:35 ` Martin Schlemmer
2003-09-07 0:06 ` Luke-Jr
2003-09-07 1:12 ` Martin Schlemmer
2003-09-06 8:48 ` Philippe Lafoucrière
2003-09-04 19:14 ` Luke-Jr
2003-09-04 19:42 ` Camille Huot
2003-09-04 19:45 ` Luke-Jr
2003-09-04 20:47 ` George Shapovalov
2003-09-04 20:52 ` Jean Jordaan
2003-09-04 22:09 ` Grant Goodyear
2003-09-04 22:26 ` Luke-Jr
2003-09-05 8:19 ` Jean Jordaan
2003-09-04 23:41 ` Daniel Robbins
2003-09-04 22:14 ` Jan Krueger
2003-09-05 8:22 ` [gentoo-dev] " Philippe Lafoucrière
2003-09-05 8:51 ` Ralph F. De Witt
2003-09-05 12:29 ` Mike Frysinger
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=20030906035000.17fcce74.degrenier@easyconnect.fr \
--to=degrenier@easyconnect.fr \
--cc=gentoo-dev@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