Carlos Silva wrote:
> On Fri, 2006-02-03 at 10:19 +0000, Francesco Riosa wrote:
>> Ok, I've been realized that having a slotted mysql is not the dream of
>> every end user ... or developer.
>>
>> Anyway I prefere too keep the possibility to do a similar install.
>>
>> A good solution should be to add the "multislot" USE flag to the ebuild
>> and let it to decide whenever make it slotted or not, sorry, this is not
>> viable, yes it's already used by other important packages but not well
>> supported by portage and should be used only in particular situations.
>>
>> The only thing that came in mind to me is to provide two series of
>> ebuilds, with different revision ranges.
>> The use flag "multislot" will still have a role, to make the ebuild fail
>> during pkg_setup() if set on the wrong ebuild.
>> It's possible to define the default ebuild to merge, assigning a greater
>> revision number will make an ebuild the default installed, I suggest the
>> un-slotted version to be the default.
>>
>> example:
>>
>> mysql-4.1.16-r[0..49] Need "+multislot"
>> mysql-4.1.16-r[50..99] Need "-multislot"
>> mysql-5.1.18-r[0..49] Need "+multislot"
>> mysql-5.1.18-r[50..99] Need "-multislot"
>>
>> whoever want to have a slot version will need to mask revisions between
>> 50 and 99 .
>>
>> The change will happen soon, between today and tomorrow, so toughts,
>> flames and insults are well accepted.
>>
>> - Francesco R.
> I really don't like this... It will give users more work to maintain
> their systems... Managing /etc/portage/ isn't easy, and forcing the
> users to use it, isn't good too. I speak for mysql:
> [EMAIL PROTECTED] ~ $ cat /etc/portage/package.keywords | wc -l
> 53
> ^^ And this was about 100 before i did a cleanup to it.
>
> What i sugest is to create a diferent package, mysql-{slotted,}. You
> guys from the mysql herd can use the same ebuils to both packages (the
> content i mean) and just check the ${PN} for the slotted word to see if
> the package is slotted or not....
>
> Just my 0.02€
>
I'm going to assume that user _don't_ want a slotted mysql .
Not forcing the users to mess with /etc/portage is exactly what I try to
achieve here.
Assuming the ebuilds are already marked stable (and btw un-slotted MUST
be marked stable before or at the same time then slotted).
This case if u remove totally /etc/portage you will have a un-slotted
mysql installed, of the best version avaiable, isn't this what we want
to achieve ?
Having a different package is doable but also a un-useful tree cluttering.
Also I assume that if the user want to have a slotted MySQL version
he/she/they can cope with some entries in /etc/portage to achieve the
result.
--
gentoo-dev@gentoo.org mailing list
