Comments for Divagations of a developer http://baraujo.net/blog Thoughts about software development, information retrieval and sometimes about fun stuff Tue, 13 Apr 2010 09:43:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on An example of transitional packages in Debian by gregoa http://baraujo.net/blog/?p=17&cpage=1#comment-485 gregoa Tue, 13 Apr 2010 09:43:56 +0000 http://baraujo.net/blog/?p=17#comment-485 cf. also http://wiki.debian.org/Renaming_a_Package cf. also http://wiki.debian.org/Renaming_a_Package

]]> Comment on An example of transitional packages in Debian by Vincent Danjean http://baraujo.net/blog/?p=17&cpage=1#comment-484 Vincent Danjean Tue, 13 Apr 2010 08:58:39 +0000 http://baraujo.net/blog/?p=17#comment-484 Hi, You are missing a problem (for which I do not know any solution) about auto/manual package. If a user install the (old) package foo "apt-get install foo" and then upgrade its system when the new packages (new foo and bar) are available "apt-get dist-upgrade", due to dependencies, bar will be pulled be new foo. But, if, reading the description of new foo, the user type "apt-get remove foo", then the next "apt-get autoremove" will remove bar... Indeed, old foo was a package installed manually. bar has been installed automatically by new foo. apt-get and aptitude does not know anything (yet) about transitional packages. So, when removing new foo, apt-get and aptitude propose to also remove its dependencies... I thing that the solution will require some logic into apt-get/aptitude AND some information in the package itself (transitions are not always a simple as one package replaced by one package). But nothing is done for now. Hi,
You are missing a problem (for which I do not know any solution) about auto/manual package.
If a user install the (old) package foo “apt-get install foo” and then upgrade its system when the new packages (new foo and bar) are available “apt-get dist-upgrade”, due to dependencies, bar will be pulled be new foo.
But, if, reading the description of new foo, the user type “apt-get remove foo”, then the next “apt-get autoremove” will remove bar…
Indeed, old foo was a package installed manually. bar has been installed automatically by new foo. apt-get and aptitude does not know anything (yet) about transitional packages. So, when removing new foo, apt-get and aptitude propose to also remove its dependencies…

I thing that the solution will require some logic into apt-get/aptitude AND some information in the package itself (transitions are not always a simple as one package replaced by one package). But nothing is done for now.

]]> Comment on An example of transitional packages in Debian by poinfestion http://baraujo.net/blog/?p=17&cpage=1#comment-245 poinfestion Sat, 02 Jan 2010 09:09:19 +0000 http://baraujo.net/blog/?p=17#comment-245 Sry for writing off topic but what WordPress template do you use? It looks interesting!! Sry for writing off topic but what WordPress template do you use? It looks interesting!!

]]>