hi there,

it is time for another of my biweekly snapshot upgrade.

this is what i see this time during the update process:

Candidates for updating php5-gd-5.2.9 -> php5-gd-5.2.9 php5-gd-5.2.9-no_x11
Ambiguous: choose package for php5-gd-5.2.9
         0: <None>
         1: php5-gd-5.2.9
         2: php5-gd-5.2.9-no_x11
Your choice: 1

i can undarstand the point of these questions when installing
a new package as it is really ambiguous what i might want.
but during the upgrade i think it is quite obvious what is my choice.

i know that doing the version number parsing dance is difficult,
but would it be difficult to teach pkg_add to pick the same flavour
of a particular package when doing the upgrade?  is this feasable?

Candidates for updating py-Imaging-1.1.6p0-python2.5 -> 
py-Imaging-1.1.6p0-python2.5 py-Imaging-1.1.6p0-python2.4
Ambiguous: choose package for py-Imaging-1.1.6p0-python2.5
         0: <None>
         1: py-Imaging-1.1.6p0-python2.4
         2: py-Imaging-1.1.6p0-python2.5
Your choice: 2

this case is not so trivial...  what would happen if i chose (1)?
would it then pull in python 2.4 as a dependency?  obviously, in
this case it is not desirable (for me) but does pkg_add handle
additional new dependencies of an upgrade?  say the upgrade of
midnight commander suddenly had another package as run dependancy
that the previous version did not have....

-f
-- 
what we do not understand we do not possess. -- goethe

Reply via email to