| 1 |
Carlos Silva wrote: |
| 2 |
> On Fri, 2006-02-03 at 10:19 +0000, Francesco Riosa wrote: |
| 3 |
>> Ok, I've been realized that having a slotted mysql is not the dream of |
| 4 |
>> every end user ... or developer. |
| 5 |
>> |
| 6 |
>> Anyway I prefere too keep the possibility to do a similar install. |
| 7 |
>> |
| 8 |
>> A good solution should be to add the "multislot" USE flag to the ebuild |
| 9 |
>> and let it to decide whenever make it slotted or not, sorry, this is not |
| 10 |
>> viable, yes it's already used by other important packages but not well |
| 11 |
>> supported by portage and should be used only in particular situations. |
| 12 |
>> |
| 13 |
>> The only thing that came in mind to me is to provide two series of |
| 14 |
>> ebuilds, with different revision ranges. |
| 15 |
>> The use flag "multislot" will still have a role, to make the ebuild fail |
| 16 |
>> during pkg_setup() if set on the wrong ebuild. |
| 17 |
>> It's possible to define the default ebuild to merge, assigning a greater |
| 18 |
>> revision number will make an ebuild the default installed, I suggest the |
| 19 |
>> un-slotted version to be the default. |
| 20 |
>> |
| 21 |
>> example: |
| 22 |
>> |
| 23 |
>> mysql-4.1.16-r[0..49] Need "+multislot" |
| 24 |
>> mysql-4.1.16-r[50..99] Need "-multislot" |
| 25 |
>> mysql-5.1.18-r[0..49] Need "+multislot" |
| 26 |
>> mysql-5.1.18-r[50..99] Need "-multislot" |
| 27 |
>> |
| 28 |
>> whoever want to have a slot version will need to mask revisions between |
| 29 |
>> 50 and 99 . |
| 30 |
>> |
| 31 |
>> The change will happen soon, between today and tomorrow, so toughts, |
| 32 |
>> flames and insults are well accepted. |
| 33 |
>> |
| 34 |
>> - Francesco R. |
| 35 |
> I really don't like this... It will give users more work to maintain |
| 36 |
> their systems... Managing /etc/portage/ isn't easy, and forcing the |
| 37 |
> users to use it, isn't good too. I speak for mysql: |
| 38 |
> r3pek@morpheus ~ $ cat /etc/portage/package.keywords | wc -l |
| 39 |
> 53 |
| 40 |
> ^^ And this was about 100 before i did a cleanup to it. |
| 41 |
> |
| 42 |
> What i sugest is to create a diferent package, mysql-{slotted,}. You |
| 43 |
> guys from the mysql herd can use the same ebuils to both packages (the |
| 44 |
> content i mean) and just check the ${PN} for the slotted word to see if |
| 45 |
> the package is slotted or not.... |
| 46 |
> |
| 47 |
> Just my 0.02ยค |
| 48 |
> |
| 49 |
|
| 50 |
I'm going to assume that user _don't_ want a slotted mysql . |
| 51 |
|
| 52 |
Not forcing the users to mess with /etc/portage is exactly what I try to |
| 53 |
achieve here. |
| 54 |
|
| 55 |
Assuming the ebuilds are already marked stable (and btw un-slotted MUST |
| 56 |
be marked stable before or at the same time then slotted). |
| 57 |
This case if u remove totally /etc/portage you will have a un-slotted |
| 58 |
mysql installed, of the best version avaiable, isn't this what we want |
| 59 |
to achieve ? |
| 60 |
|
| 61 |
Having a different package is doable but also a un-useful tree cluttering. |
| 62 |
|
| 63 |
Also I assume that if the user want to have a slotted MySQL version |
| 64 |
he/she/they can cope with some entries in /etc/portage to achieve the |
| 65 |
result. |
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
-- |
| 70 |
gentoo-dev@g.o mailing list |
Archives