From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-portage-dev@gentoo.org
Subject: Re: [gentoo-portage-dev] RFC on a "slot" update command
Date: Tue, 04 Nov 2003 08:57:29 -0700 [thread overview]
Message-ID: <1067961449.12499.1.camel@ht.gentoo.org> (raw)
In-Reply-To: <20031104155720.3bd68726.degrenier@easyconnect.fr>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
On Tue, 2003-11-04 at 07:57, Thomas de Grenier de Latour wrote:
> I've suggested this portage feature some time ago:
> http://bugs.gentoo.org/show_bug.cgi?id=27965
>
> Taking the ruby package as an example, the update command could have
> been something like this:
> "slot dev-lang/ruby-1.8* dev-lang/ruby-1.8* 1.8"
This is needed. I've added this email to my "portage-fixes" folder,
which means we'll keep this issue in mind when designing the
architecture for portage-ng.
Regards,
Daniel
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-11-04 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 14:57 [gentoo-portage-dev] RFC on a "slot" update command Thomas de Grenier de Latour
2003-11-04 15:57 ` Daniel Robbins [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=1067961449.12499.1.camel@ht.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-portage-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