From: Marius Mauch <genone@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 15:18:51 +0200 [thread overview]
Message-ID: <20041023151851.7fe58f1a@andy.genone.homeip.net> (raw)
In-Reply-To: <20041023121715.78153.qmail@web41524.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 10/23/04 Pablo De Napoli wrote:
> 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 never really worked. It did a lookup from the given filename in the
portage tree and converted the filename to a cpv entry (as most portage
functions only deal with cpv entries and not full filenames). This means
that in some situations portage used a different ebuild than you
specified.
It also had several side effects that aren't documented and caused bogus
bugreports.
> 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.
To keep the quality we added those warnings. These features (I don't
consider them important) were always broken, to fix them we'd have to
re-implement them completely and make several API changes.
Marius
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-23 13:18 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 [this message]
2004-10-23 13:50 ` Jason Stubbs
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=20041023151851.7fe58f1a@andy.genone.homeip.net \
--to=genone@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