[gentoo-dev] missing SLOTs

[gentoo-dev] missing SLOTs

[Jani Monoses]

After looking at why emerge clean wouldn't get rid of older hdparm and openssh I found that 
the ebuilds for the old versions didn't have a SLOT so portage assumes nothing != 0 and
keeps both versions.
But aren't all ebuilds supposed to have SLOT defined?
Maybe temporarily until all such cases are fixed emerge could presume missing slot means 0?

And if this should be a bug-report would it be much harder for the core portage tree maintainters 
to have ebuild fixes and submits dealt with on a separate mailing list instead of bugzilla.
I personally find the latter horrible and a lot harder to use than simply mailing a patch 
but again that's just my oppinion.Another benefit of a mailing list would be that people 
subscribed would see if/when new ebuilds are worked on.Maybe one can subscribe to bugzilla
as well but sometimes ebuilds are put in another bug category...I'll just stop now.

Re: [gentoo-dev] missing SLOTs

[Mark Gilbert]

Eh, problem with hdparm is that 5.2 is being merged in /usr/sbin while
4.9 sits in /sbin.

-MG

On Fri, 2002-07-12 at 21:11, Bob Phan wrote:
> * On Jun 27, 2002, Jani Monoses <jani@iv.ro> said:
> > After looking at why emerge clean wouldn't get rid of older hdparm and openssh I found that 
> > the ebuilds for the old versions didn't have a SLOT so portage assumes nothing != 0 and
> > keeps both versions.
> > But aren't all ebuilds supposed to have SLOT defined?
> > Maybe temporarily until all such cases are fixed emerge could presume missing slot means 0?
> 
> Generally speaking, it is better to assume too little than too much.
> Let's say that there is a library that you want to keep around without a
> slot and one of the same name at slot 0 (hypothetically, because I can't
> come up with an actual instance of this).  Each and every time you try
> to clean your packages, it annoyingly uninstalls the unslotted package.
> On the other hand, you notice that one package didn't get uninstalled
> that you think should have been.  You go ahead and uninstall the package
> and never hear from it again.  That's why the current model is safer, at
> the cost of a single minor annoyance as opposed to repeated annoyance.
> 
> But I do agree that all packages should be slotted and, if I'm not
> mistaken, they'll all have slots eventually.  It's just a matter of
> waiting it out.
> 
> -- 
> /*
>  * Bob Phan <bob@endlessrecursion.net,rphan@nrgn.com>
>  * Computational Chemistry Informatics
>  * Neurogen Corporation
>  * (203)488-8201 x4645
>  *
>  * To understand recursion, you must first understand recursion.
>  * http://www.endlessrecursion.net/
>  */
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
-- 
<<anonymous>> ...for a brief period in the late ninetys, the rare
ability of pulling money out of ones arse flourished

Re: [gentoo-dev] missing SLOTs

[Bob Phan]

* On Jun 27, 2002, Jani Monoses <jani@iv.ro> said:
> After looking at why emerge clean wouldn't get rid of older hdparm and openssh I found that 
> the ebuilds for the old versions didn't have a SLOT so portage assumes nothing != 0 and
> keeps both versions.
> But aren't all ebuilds supposed to have SLOT defined?
> Maybe temporarily until all such cases are fixed emerge could presume missing slot means 0?

Generally speaking, it is better to assume too little than too much.
Let's say that there is a library that you want to keep around without a
slot and one of the same name at slot 0 (hypothetically, because I can't
come up with an actual instance of this).  Each and every time you try
to clean your packages, it annoyingly uninstalls the unslotted package.
On the other hand, you notice that one package didn't get uninstalled
that you think should have been.  You go ahead and uninstall the package
and never hear from it again.  That's why the current model is safer, at
the cost of a single minor annoyance as opposed to repeated annoyance.

But I do agree that all packages should be slotted and, if I'm not
mistaken, they'll all have slots eventually.  It's just a matter of
waiting it out.

-- 
/*
 * Bob Phan <bob@endlessrecursion.net,rphan@nrgn.com>
 * Computational Chemistry Informatics
 * Neurogen Corporation
 * (203)488-8201 x4645
 *
 * To understand recursion, you must first understand recursion.
 * http://www.endlessrecursion.net/
 */