From: Ben Lutgens <blutgens@sistina.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuild
Date: Sat May 26 12:08:02 2001 [thread overview]
Message-ID: <20010526130441.A26510@ares> (raw)
In-Reply-To: <200105251839957.SM00748@m2w031>; from kevin@silversoftware.org on Fri, May 25, 2001 at 06:39:52PM -0400
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Fri, May 25, 2001 at 06:39:52PM -0400, kevin@silversoftware.org wrote:
>Dev,
>
>I apologize for my ignorance, but is there an ebuild command that checks the packages you have already installed and upgrades them all at once? Or do I manually upgrade each package? I see advantages to both methods.
emerge will do that. ebuild is the lowerlevel tool. Think of emerge as a
"front end" of sorts.
>
>Thanks in advance.
>
>
>-Kevin Radcliffe
>
>
>
>--------------------------------------------------------------------
>Mail2Web - Check your email from the web at
>http://www.mail2web.com/ .
>
>
>_______________________________________________
>gentoo-dev mailing list
>gentoo-dev@gentoo.org
>http://www.gentoo.org/mailman/listinfo/gentoo-dev
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-05-26 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 16:41 [gentoo-dev] Ebuild kevin
2001-05-26 12:08 ` Ben Lutgens [this message]
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=20010526130441.A26510@ares \
--to=blutgens@sistina.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