From: "Mike Myers" <fluffymikey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] anti-portage wreckage?
Date: Mon, 25 Dec 2006 22:41:52 -0600 [thread overview]
Message-ID: <89646b4a0612252041h257e8fc7pa057ac2016e04f26@mail.gmail.com> (raw)
In-Reply-To: <200612251817.17416.bss03@volumehost.net>
[-- Attachment #1: Type: text/plain, Size: 1934 bytes --]
On 12/25/06, Boyd Stephen Smith Jr. <bss03@volumehost.net> wrote:
>
> On Monday 25 December 2006 14:09, "Mike Myers" <fluffymikey@gmail.com>
> wrote about 'Re: [gentoo-user] anti-portage wreckage?':
> > I understand the portage system enough to mask
> > the packages I don't want, but then there's the problem of other updates
> > requiring that package.
>
> Well, either (a) the new version is required, so you'll have to upgrade to
> the other package as well or (b) a developer was sloppy with dependencies,
> and you need to file a bug to change them.
>
> > Anyways, all I'm essentially asking for is a way to separate minor
> > updates from major updates.
>
> With some of the advanced atom operators (particularly '*' and '~'), you
> should be able to specify exactly what level of masking you want. I
> believe this is documented in 'man ebuild' but I'm not sure; 'man portage'
> is a decent place to start your search for the atom syntax you need.
>
> You could also make your own profile that does "cap" packges at a certain
> version and have it's parent be an established profile, although I'm not
> sure that bit of portage hackery is supported.
I know these things could be done, but I don't really think it's worth it.
The problem is that these kinds of solutions don't scale very well.. they
don't really scale at all really. If I have to reinstall for whatever
reason, then I have to redo all this hackery, as you put it, heh. In any
case, this is still a bit of a reactive approach, since I have to be aware
that there may be a problem with a particular update before I know to mask
it. I really like the idea of the tree version thing though. I'll see if
there's anything I can do to support that.
PS:
> A: Because it reverses the order of the "conversation".
> Q: Why is top-posting so annoying?
> A: Top-posting.
> Q: What's the most annoying thing on newsgroups and mailing lists.
PS:
Noted! Sorry :P
[-- Attachment #2: Type: text/html, Size: 2655 bytes --]
next prev parent reply other threads:[~2006-12-26 4:45 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 1:52 [gentoo-user] anti-portage wreckage? Mike Myers
2006-12-24 14:29 ` david
2006-12-25 3:01 ` Mike Myers
2006-12-25 6:36 ` Andrey Gerasimenko
2006-12-25 8:46 ` Mike Myers
2006-12-25 9:06 ` Dale
2006-12-25 10:48 ` Andrey Gerasimenko
2006-12-25 12:11 ` Boyd Stephen Smith Jr.
2006-12-25 12:04 ` Boyd Stephen Smith Jr.
2006-12-25 20:09 ` Mike Myers
2006-12-26 0:17 ` Boyd Stephen Smith Jr.
2006-12-26 4:41 ` Mike Myers [this message]
2006-12-26 13:28 ` Boyd Stephen Smith Jr.
2006-12-25 20:15 ` Richard Fish
2006-12-25 20:34 ` Mike Myers
2006-12-26 15:56 ` [gentoo-user] " James
2006-12-26 20:02 ` Uwe Thiem
2006-12-27 9:45 ` Mike Myers
2006-12-27 22:14 ` James
2006-12-27 22:43 ` Mike Myers
2006-12-31 12:18 ` Aniruddha
2006-12-31 13:40 ` Mick
2006-12-31 16:02 ` Uwe Thiem
2006-12-31 18:20 ` Mick
2006-12-31 18:57 ` Michal 'vorner' Vaner
2006-12-31 20:50 ` Uwe Thiem
2006-12-31 20:48 ` Uwe Thiem
2006-12-31 23:29 ` Mike Myers
2007-01-01 1:01 ` Mike Myers
2007-01-01 1:34 ` Mark Kirkwood
2007-01-01 2:27 ` Mark Knecht
2007-01-01 2:36 ` Mike Myers
2007-01-01 1:40 ` Neil Walker
2007-01-01 2:34 ` Mike Myers
2007-01-01 10:36 ` Mark Kirkwood
2007-01-02 10:32 ` Neil Bothwick
2007-01-01 20:08 ` Aniruddha
2007-01-02 6:50 ` Daniel Barkalow
2007-01-02 9:11 ` Neil Bothwick
2007-01-03 5:45 ` Daniel Barkalow
2007-01-03 8:56 ` Neil Bothwick
2007-01-03 21:02 ` Daniel Barkalow
[not found] ` <20070104084454.261923bc@krikkit.digimed.co.uk>
2007-01-04 10:20 ` Bo Ørsted Andresen
2007-01-02 10:02 ` Alan McKinnon
2007-01-03 5:21 ` Daniel Barkalow
2007-01-03 7:47 ` Alan McKinnon
2007-01-03 18:24 ` Daniel Barkalow
2007-01-03 23:44 ` Alan McKinnon
2007-01-06 6:43 ` Daniel Barkalow
2007-01-06 14:11 ` Boyd Stephen Smith Jr.
2007-01-03 8:58 ` Neil Bothwick
2007-01-03 11:03 ` Nelson, David (ED, PAR&D)
2007-01-03 11:42 ` Hans-Werner Hilse
2007-01-03 11:51 ` Alan McKinnon
2007-01-03 13:04 ` Neil Bothwick
2007-01-03 20:29 ` Daniel Barkalow
2007-01-02 9:58 ` Alan McKinnon
2007-01-04 8:43 ` Mike Myers
2007-01-01 2:45 ` William Kenworthy
2007-01-01 4:35 ` Richard Fish
2007-01-01 5:58 ` William Kenworthy
2007-01-02 11:19 ` Bo Ørsted Andresen
2007-01-02 13:26 ` William Kenworthy
2007-01-03 13:52 ` Bo Ørsted Andresen
2007-01-01 10:37 ` Neil Bothwick
2007-01-02 18:28 ` Andrey Gerasimenko
2006-12-31 22:19 ` [gentoo-user] " Aniruddha
2007-01-01 1:49 ` Neil Walker
2006-12-31 22:20 ` Aniruddha
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=89646b4a0612252041h257e8fc7pa057ac2016e04f26@mail.gmail.com \
--to=fluffymikey@gmail.com \
--cc=gentoo-user@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