public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] Breaking up the beast known as app-games
Date: Fri, 5 Sep 2003 00:13:17 -0400	[thread overview]
Message-ID: <200309050013.33902.vapier@gentoo.org> (raw)
In-Reply-To: <20030904221405.6f2b9f22.degrenier@easyconnect.fr>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 905 bytes --]

On Thursday 04 September 2003 16:14, Thomas de Grenier de Latour wrote:
> On Thu, 4 Sep 2003 21:45:30 +0200
>
> Camille Huot <cam@cameuh.net> wrote:
> > sounds nice. I think there is some work to be done to portage to get
> > this working.
>
> I don't see the main difficulty in modifying portage, but rather in
> doing the transition to the new tree without breaking backward
> compatibility with old installed portage versions. There are some
> people, especialy those who run gentoo on production servers, who don't
> do their weekly deep update :/

nah, if we change the rsync targets ... :)
then have the 'next gen' of portage sync against the new target ... old people 
wouldnt get updates so they'd be encouraged to upgrade their portage and 
update the rsync target ...

i'm not saying that this rsync is the answer ... the point is that it can be 
done semi-easily ...
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2003-09-05  4:13 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 [this message]
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
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=200309050013.33902.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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