public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage 1.8.1 released
Date: Sun, 30 Dec 2001 10:28:11 -0600	[thread overview]
Message-ID: <20011230102811.B19237@chiba.3jane.net> (raw)
In-Reply-To: <0GP500L0BG1EKS@mxout2.netvision.net.il>

On Sun, Dec 30, 2001 at 10:55:01AM +0200, Dan Armak wrote:
> > For really large packages it might be nice if we did diff's and uploaded
> > to ibiblio.
> I'm probably dreaming here, but maybe we coud have some diff auto-generating 
> system, which could provide a diff between any two versions, like cvs does. 
> But that's far in the future, if it happens at all.

I agree here.  All developers should use complete sources, and we should work
towards creating a more generic solution to this problem.  With a bit of 
Portage glue, a user with linux-2.4.16.tar.bz2 on his hard drive can have
Portage auto-download a patch, and then *create* linux-2.4.17.tar.bz2 for him.
If this is done correctly, the md5's will be the same and developers can always
use the full version of the archive rather than a patch in their ebuilds.

Best Regards,

-- 
Daniel Robbins                                  <drobbins@gentoo.org>
Chief Architect/President                       http://www.gentoo.org 
Gentoo Technologies, Inc.


  reply	other threads:[~2001-12-30 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-30  6:56 [gentoo-dev] Portage 1.8.1 released Daniel Robbins
2001-12-30  7:46 ` slik
2001-12-30  7:52   ` MIkael Hallendal
2001-12-30  8:55     ` Dan Armak
2001-12-30 16:28       ` Daniel Robbins [this message]
2001-12-30  9:20 ` Dan Armak
2001-12-30 16:29   ` Daniel Robbins
2001-12-30 12:04 ` Sebastian Werner
2001-12-30 20:57   ` Sebastian Werner
2001-12-30 21:51 ` jano
2001-12-30 21:42   ` Daniel Robbins

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=20011230102811.B19237@chiba.3jane.net \
    --to=drobbins@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