public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: MIkael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage 1.8.1 released
Date: 30 Dec 2001 08:52:02 +0100	[thread overview]
Message-ID: <1009698724.11092.2.camel@fluffy> (raw)
In-Reply-To: <3C2EC667.D4D398CF@telusplanet.net>

sön 2001-12-30 klockan 08.46 skrev slik@telusplanet.net:
> Daniel Robbins wrote:
> > 
> > Hi All,
> > 
> > Portage 1.8.1 has been released, which now includes working "emerge update"
> > functionality.  "emerge update" allows you to keep your key Gentoo Linux
> > system packages fully up-to-date.  To use it, first type "emerge --pretend
> > update" to
> 
> Will this download and apply patches to previous source releases, if
> they are available for a package? i.e. kernel,emacs,glibc,gnome,kde? are
> very large. (very handy for those with slow connections!)

This depends on how the person that upgraded the package did it. 

With this functionality all developers should try to use patches rather
than the full file (if they are available). I come to think of the
kernel-sources which always provides patches for updating.

For really large packages it might be nice if we did diff's and uploaded
to ibiblio.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden




  reply	other threads:[~2001-12-30  7:51 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 [this message]
2001-12-30  8:55     ` Dan Armak
2001-12-30 16:28       ` Daniel Robbins
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=1009698724.11092.2.camel@fluffy \
    --to=hallski@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