public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Luke-Jr <luke-jr@gentoo.org>
Cc: Yuri Enshin <kot@formoza-centre.ru>, Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] reason for dhcpcd in system profile ?
Date: Mon, 25 Aug 2003 06:24:15 +0200	[thread overview]
Message-ID: <1061785455.13460.37.camel@nosferatu.lan> (raw)
In-Reply-To: <200308250219.08409.luke-jr@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On Mon, 2003-08-25 at 04:18, Luke-Jr wrote:
> >
> > > If rsync is in system, it probably should be removed. Portage could quite
> > > easilly just install it when the user tries to sync if need be.
> >
> > So we devs are going to start moaning because we have rsync installed ?
> I doubt anyone is going to whine because they have something they don't need 
> installed. The reason to whine is because it's installed *by default*. rsync 
> is really cool, but it doesn't really have any reason for being installed 
> before the user wants it.

So it is not used anymore to fetch the portage tree when a user
'emerge sync' ?


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-25  4:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 19:04 [gentoo-dev] reason for dhcpcd in system profile ? Marius Mauch
2003-08-23 19:20 ` Wolfram Schlich
2003-08-23 20:23   ` Daniel Armyr
2003-08-23 21:20     ` Wolfram Schlich
2003-08-24  6:08       ` Daniel Armyr
2003-08-23 23:06   ` Luke-Jr
2003-08-24  3:21     ` A. Craig West
2003-08-24  8:59       ` Spider
2003-08-24 16:32         ` Alec Berryman
2003-08-24 16:44           ` Spider
2003-08-24 18:16             ` Paul de Vrieze
2003-08-24 18:40               ` Alec Berryman
2003-08-24 18:55               ` Andrew Gaffney
2003-08-24 18:47                 ` Paul de Vrieze
2003-08-24 19:05                   ` Andrew Gaffney
2003-08-24 19:03                     ` Marius Mauch
2003-08-25  0:44                       ` Andrew Gaffney
2003-08-25  0:48                         ` Andrew Gaffney
2003-08-24 22:00         ` Grant Goodyear
2003-08-25  3:07         ` Luke-Jr
2003-08-23 19:29 ` Stewart Honsberger
2003-08-23 20:29   ` Kevyn Shortell
2003-08-24  7:22     ` Stewart Honsberger
2003-08-24  8:33       ` Kevyn Shortell
2003-08-24 15:09         ` Brad Laue
2003-08-24 20:41           ` Kevyn Shortell
2003-08-23 21:25   ` Norberto BENSA
2003-08-23 20:34 ` Yuri Enshin
2003-08-23 21:27   ` Norberto BENSA
2003-08-23 23:16   ` Luke-Jr
2003-08-24  8:15     ` Martin Schlemmer
2003-08-25  2:18       ` Luke-Jr
2003-08-25  4:24         ` Martin Schlemmer [this message]
2003-08-25  4:46         ` Martin Schlemmer
2003-08-25 13:46           ` Luke-Jr
2003-08-25 16:27   ` William Hubbs
2003-08-23 23:08 ` Lloyd D Budd
2003-08-24  4:28   ` Andrew Gaffney
2003-08-24 14:14 ` Marius Mauch
2003-08-24 14:33   ` Martin Schlemmer
2003-08-24 15:09     ` Paul de Vrieze
  -- strict thread matches above, loose matches on Subject: below --
2003-08-24 20:40 Spider

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=1061785455.13460.37.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=kot@formoza-centre.ru \
    --cc=luke-jr@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