[Slapt-get-user] slapt-get dependency question/bug?

Jason Woodward woodwardj at jaos.org
Tue Mar 15 01:45:49 EST 2005


Hi Paul,

> Here's the scenario (package names have been simplified):
>   package_a-1.0 {requires: package_b >= 2.0
>                  requires: package_c >= 1.0
>                  package_a has not been previously installed}
>   package_b-2.0 {package_b-1.0 is currently installed}
>   package_c-1.0 {package_c has not been previously installed}
> 
> If I were to run 'slapt-get --install package_a' I would expect that
> package_c and package_b would be installed (probably package_c first, then
> package_b based on new install versus an upgrade), followed by package_a.
> 
> However, package_a actually gets installed after package_c.  Package_b is
> the last one installed.  All packages do ultimately get installed, but
> this can lead to some problems at least for the enviroment I'm in.
> 
> Any insight on this would be appreciated.

Packages c and a are installed.  Package b is then upgraded.  New installs happen before
upgrades.  The actual order of discovery follows your expectations but in executing the pending
changes, the installs are prioritized higher than upgrades.


take care,
jason



More information about the Slapt-get-user mailing list