public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eugene Wong" <disposable_eugene@hotmail.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Portage as a dependency
Date: Fri, 07 Feb 2003 10:32:27 -0800	[thread overview]
Message-ID: <F128T3kLCXAUxD2wjC90000f8d9@hotmail.com> (raw)

>From: Alain Penders <alain@gentoo.org>
>To: gentoo-dev@gentoo.org
>Subject: Re: [gentoo-dev] Portage as a dependency
>Date: Fri, 7 Feb 2003 10:06:47 -0700
>
>I would hope that people rsync before installing new packages -- saves 
>having
>to install them twice.  After the rsync, if you run emerge -up world, 
>you'll
>get a specific message in the package list about a new portage being
>available.  Isn't this and the general knowledge that Gentoo hinges on 
>portage
>enough for people to update portage before emerging other packages?

Well, it wasn't entirely obvious to me. However, that's probably because I'm 
too new @ the concept of portage. If you guys are going after a certain type 
of technical user, then it's no big deal, but if you are going after user 
friendliness, then there should be more done to prevent problems.


Sincerely, and with thanks,
Eugene T.S. Wong

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-02-07 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 18:32 Eugene Wong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-11 16:54 [gentoo-dev] Portage as a dependency Sean P. Kane
2003-02-07 17:06 Sean P. Kane
2003-02-07 16:49 Sean P. Kane
2003-02-07 17:06 ` Alain Penders
2003-02-07 17:34   ` Toby Dickenson
2003-02-06 23:17 Sean P. Kane
2003-02-07  3:30 ` Dylan Carlson

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=F128T3kLCXAUxD2wjC90000f8d9@hotmail.com \
    --to=disposable_eugene@hotmail.com \
    --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