From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] two remarks on portage-2.0.51-r2
Date: Sat, 23 Oct 2004 22:50:55 +0900 [thread overview]
Message-ID: <200410232250.55610.jstubbs@gentoo.org> (raw)
In-Reply-To: <20041023121715.78153.qmail@web41524.mail.yahoo.com>
On Saturday 23 October 2004 21:17, Pablo De Napoli wrote:
> I see that portage-2.0.51-r2 is now stable.
> However, It has some useful features that are deprecated or broken.
>
> 1) emerge --upgradeonly
>
> Why is this deprecated? I think it is endeed a useful feature.
> I'm not sure that the files /etc/portage/package* are a good (esay-to-use)
> replacement for it.
Downgrades happen when:
* a package's versioning changes and it is actually an upgrade,
* a package is broken and dangerous, or
* masking has been bypassed in some way.
In the first two cases, you want the change to happen. In the
third, /etc/portage/package* serves you much better.
> 2) emerge ebuild by path
>
> Acording to the man page, this is broken, however it is the most obvious
> way to specify an ebuild, isn't it?
>
> Why is this feature broken, could anybody find out?
It was always broken. It is fact now slightly less broken than it was in
2.0.50. At least now it'll prevent tell you when you are going to install
something unmasked - which is it's main use by developers - and actually
cancel the merge when it's not about to merge that which you asked for.
> I think is very important to keep the quality of portage to the highest
> standards, so I suggest not to realese as stable a version with important
> features broken.
No offense but I find this almost comical. Have a look on bugs.g.o for portage
bugs. You'd be surprised I think. 2.0.51 has bugs - even a couple of new ones
that should be fixed soon - but there's nothing really broken that wasn't
broken before.
Regards,
Jason Stubbs
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-23 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 12:17 [gentoo-portage-dev] two remarks on portage-2.0.51-r2 Pablo De Napoli
2004-10-23 12:30 ` Roman Gaufman
2004-10-23 12:36 ` Roman Gaufman
2004-10-23 13:18 ` Marius Mauch
2004-10-23 13:50 ` Jason Stubbs [this message]
2004-10-23 18:33 ` Pablo De Napoli
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=200410232250.55610.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-portage-dev@lists.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