Dependencies to special versions
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have a problem with dependencies in some of my packages:
There is a "task" package which just depends on the concrete version
of the children. It looks like this:
- - debian/contrl -----------------------
Package: foo
Depends: foo-doc (= ${Source-Version}), foo-misc (= ${Source-Version})
...
Package: foo-misc
Depends: ${shlibs:Depends}
...
Package: foo-doc
...
- --------------------------------------------
When I have installed an old version, say foo-1.0-1 and its children
with the same version, foo will depend on foo-doc-1.0-1 and
foo-misc-1.0-1.
Now I create a new version 1.0-2 of all packages and try to upgrade.
apt-get will download the files and unpacks them. Before
configuration of foo-1.0-2 it complains that foo-doc and foo-misc are
not installed in the newer version. Moreover it can't upgrade them
because it would break the dependency of the installed foo-1.0-1.
My theory is that this kind of dependencies is insane, because on
update there is no way to upgrade everything in an atomic action
which would be necessary to keep all dependencies working all the
time. Is this correct?
The work around/fix I imagine is to just depend on the package without
any revision or use something like
Depends: foo-doc (>= ${Source-Version}), foo-misc (>=
${Source-Version})
Is this correct or how would I solve a 1-1 relation between several
packages?
Thnx in advance
Schimmi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9rsfJHUDhE+YrLEURAgDaAKDzsNV0j8Nw/Ge8DibKDoxwsTKE/ACfSKxU
es2SM5CJfZdtQ7dnj8H4B3A=
=JOGR
-----END PGP SIGNATURE-----
Reply to: