[Mageia-dev] Copying dependencies from Release to Updates Testing

Samuel Verschelde stormi at laposte.net
Thu Sep 8 17:32:39 CEST 2011

Le jeudi 8 septembre 2011 14:24:38, Thierry Vignaud a écrit :
> On 8 September 2011 13:52, Balcaen John <mikala at mageia.org> wrote:
> >> Good question from MrsB : must we link only the needed binary RPMs, or
> >> all those coming from the SRPM ?
> >> 
> >> Example : qt4-database-plugin-sqlite-4.7.3-1.mga1.i586.rpm is needed,
> >> will we link all packages from the qt4 SRPM or only
> >> qt4-database-plugin- sqlite-4.7.3-1.mga1.i586.rpm ? The first option
> >> is probably cleaner, but this means copy much more packages.
> > 
> > Well we shoud links only the *requirements* for qt4-database-plugin-
> > sqlite so probably not all qt4 packages (but most of them :/ )
> No that would be only the *new requirements* of the updated package.
> Eg: if amarok doesn't with XYZ devices work because we forgot to link it
> with libXYZ, we should only copy libXYZ when uploading new amarok
> package into updates

Maybe my question was not clear : qt4-database-plugin-
sqlite-4.7.3-1.mga1.i586.rpm is needed *as a new requirement* of another 
updated package. Do we link only qt4-database-plugin-
sqlite-4.7.3-1.mga1.i586.rpm from Core Release to Updates, or do we link all 
packages from its SRPM, which is qt4 ?

Said otherwise : must we keep a coherence between RPMs and SRPMs in Core 
Updates ?


More information about the Mageia-dev mailing list