| 1 |
Le 4 nov. 2009 à 20:25, Peter Volkov a écrit : |
| 2 |
|
| 3 |
> В Срд, 04/11/2009 в 17:34 +0100, Tiziano Müller пишет: |
| 4 |
>> Am Mittwoch, den 04.11.2009, 18:44 +0300 schrieb Peter Volkov: |
| 5 |
>>> So are there any good reasons to split packages? |
| 6 |
>> |
| 7 |
>> In environments with a staging server and binary packages, yes. |
| 8 |
|
| 9 |
in case where different libs are needed in the stack but in ways that |
| 10 |
makes it do circular deps if you use an unsplitted package (think |
| 11 |
gvfs, libsoup, libproxy libsoup, and stuff like that). |
| 12 |
|
| 13 |
I think it's generally a good idea to split when the following |
| 14 |
conditions are met: |
| 15 |
* maintainer/herd has enough time to maintain the split (some splits |
| 16 |
can be time consuming) |
| 17 |
* upstream behaves nicely in the split case (splitting stuff on our |
| 18 |
own is shooting ourselves in the feet usually as is upstream not |
| 19 |
wanting to hear about it) |
| 20 |
* split benefits the user has it allows more flexibility (don't tell |
| 21 |
me about configure times, we are gentoo and flexibility most often |
| 22 |
wins over buildtime or we'd be somewhere else imho) |
| 23 |
|
| 24 |
-- |
| 25 |
Gilles Dartiguelongue <eva@g.o> |
| 26 |
Gnome team |
Archives