From: Roman Gaufman <hackeron@gmail.com>
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 12:36:13 +0000 [thread overview]
Message-ID: <921ad39e04102305361b2b61ea@mail.gmail.com> (raw)
In-Reply-To: <921ad39e04102305301f6441b5@mail.gmail.com>
Oh, just to clarify. Using emerge path-to-ebuild always had those side
effects and was only intended for developer usage to begin with!
It isnt something new in .51 -- its just finally a warning was put.
On Sat, 23 Oct 2004 12:30:45 +0000, Roman Gaufman <hackeron@gmail.com> wrote:
> 1) If you dont know how to echo package-name
> >>/etc/portage/package.keywords you shouldnt even bother with masked
> or hard masked packages.
>
> 2) Emerging path-to-ebuild doesnt append package to the world file,
> thus breaking emerge depclean and emerge -up world. --- Very bad idea
> and over long term can seriously break system concistency.
>
> To maintain the concistency of your system, allowing you to have a
> system as clean as when you installed years after, these 2 things
> should be avoided at all cost, and thus deprecated and warned highly
> against.
>
>
>
>
> On Sat, 23 Oct 2004 05:17:15 -0700 (PDT), Pablo De Napoli
> <pdenapo@yahoo.com> 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.
> >
> > 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?
> >
> > 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.
> >
> > Best regards
> >
> > Pablo De Napoli
> >
> >
> > _______________________________
> > Do you Yahoo!?
> > Declare Yourself - Register online to vote today!
> > http://vote.yahoo.com
> >
> > --
> > gentoo-portage-dev@gentoo.org mailing list
> >
> >
>
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-23 12:36 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 [this message]
2004-10-23 13:18 ` Marius Mauch
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=921ad39e04102305361b2b61ea@mail.gmail.com \
--to=hackeron@gmail.com \
--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