From: "Fabian Zeindl" <fabian@xover.htu.tuwien.ac.at>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Extended package.mask
Date: Wed, 31 Aug 2005 18:44:33 +0200 [thread overview]
Message-ID: <20050831163821.M14747@xover.htu.tuwien.ac.at> (raw)
Hi
I'm using gentoo and the best package manager of the world for over one year
now, and I'm quite satisfied :-).
One idea I had: I regularly stumble across ebuilds which are masked in
package.mask because they break certain other packages or something like that.
It would be genial if portage wouldn't just say
"this ebuild is masked cause it breaks XYZ", but detect whether I have XYZ
installed and warns me if so resp. emerges normally otherwise. If I install
package XYZ some time later portage must of course detect this and say "you
have package ABC installed, which makes problem with the package you wan't to
install now, what do you want to do?".
Is this an insane idea? It would make portage even better if it could resolve
situations/environments/configurations where emerging/unmerging something will
cause problems.
greetings
fabian zeindl
PS: The second question I want to ask: Why are some packages so long marked ~
unstable when their upstream is stable. Is there a policy how long to mark new
ebuilds or something like that?
--
... I want something good to die for
To make it beautiful to live.
I want a new mistake, lose is more than hesitate.
Do you believe it in your head?
- Queens of the Stone Age - "Go with the Flow"
I prefer signed/encrypted Mail (even if I can't write it myself at
the moment due to OpenWebMail deficiencies):
Fingerprint: CFE8 38A7 0BC4 3CB0 E454 FA8D 04F9 B3B6 E02D 25BA
--
gentoo-portage-dev@gentoo.org mailing list
next reply other threads:[~2005-08-31 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 16:44 Fabian Zeindl [this message]
2005-08-31 23:45 ` [gentoo-portage-dev] Extended package.mask Brian Harring
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=20050831163821.M14747@xover.htu.tuwien.ac.at \
--to=fabian@xover.htu.tuwien.ac.at \
--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