Yast and priorities for installation sources ?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
A question to YaST2 developers (or anyone else who'd have the answer).
I package up KDE3 styles against KDE 3.5.1 in a different repository, that must only be used when
one runs KDE 3.5. But the packages have exactly the same version and release number than the ones
that are compiled against the stock KDE 3.4.2 and that are in the "normal" suser-guru repository.
Now my question: how is YaST2 picking packages from its list of installation sources ?
Does it do some "first match wins"-alike strategy when a package with exactly the same
version+release is available from more than one installation source ?
Or is it random/unpredictable ?
cheers
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
On Wednesday 08 March 2006 07:01, Pascal Bleser wrote:
Hi
A question to YaST2 developers (or anyone else who'd have the answer).
I package up KDE3 styles against KDE 3.5.1 in a different repository, that must only be used when one runs KDE 3.5. But the packages have exactly the same version and release number than the ones that are compiled against the stock KDE 3.4.2 and that are in the "normal" suser-guru repository.
Now my question: how is YaST2 picking packages from its list of installation sources ? Does it do some "first match wins"-alike strategy when a package with exactly the same version+release is available from more than one installation source ? Or is it random/unpredictable ?
cheers
Thats a *very* good question actually. To add to that, can a preference somehow also be set for i686 over i386? I've noticed I've had to take a peek through my packages to install the version that is available and optimized for my proc, which I really would rather have automatically. Is there such a thing? Joseph M. Gaffney
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'd just like to stress this mail again, it's pretty critical for us 3rd party packagers. Could someone forward it to some yast2 developer who could answer this ? Thanks. Pascal Bleser wrote:
Hi
A question to YaST2 developers (or anyone else who'd have the answer).
I package up KDE3 styles against KDE 3.5.1 in a different repository, that must only be used when one runs KDE 3.5. But the packages have exactly the same version and release number than the ones that are compiled against the stock KDE 3.4.2 and that are in the "normal" suser-guru repository.
Now my question: how is YaST2 picking packages from its list of installation sources ? Does it do some "first match wins"-alike strategy when a package with exactly the same version+release is available from more than one installation source ? Or is it random/unpredictable ?
- --
-o) Pascal Bleser http://linux01.gwdg.de/~pbleser/
/\\
Am Sunday 12 March 2006 16:41 schrieb Pascal Bleser:
I'd just like to stress this mail again, it's pretty critical for us 3rd party packagers.
Could someone forward it to some yast2 developer who could answer this ?
until now YaST does use the newer builded package. (SL 9.1 did care about the order of the source IIRC). I am not 100% sure how it will work with 10.1 YaST, because of the new package solver. I will ask ...
Thanks.
Pascal Bleser wrote:
Hi
A question to YaST2 developers (or anyone else who'd have the answer).
I package up KDE3 styles against KDE 3.5.1 in a different repository, that must only be used when one runs KDE 3.5. But the packages have exactly the same version and release number than the ones that are compiled against the stock KDE 3.4.2 and that are in the "normal" suser-guru repository.
Now my question: how is YaST2 picking packages from its list of installation sources ? Does it do some "first match wins"-alike strategy when a package with exactly the same version+release is available from more than one installation source ? Or is it random/unpredictable ?
-- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de
participants (3)
-
Adrian Schröter -
Joseph M. Gaffney -
Pascal Bleser