Daniel Macks wrote:
[]
This falsely assumes that a .deb built for one dist will be the same
as for another.
Which, of course, has always been the fundamental assumption at the
basis of all of Fink's upgrade mechanisms when going from one tree to
another.
There's some automatic dist-dependent built-time stuff
done that may give a .deb under 10.4-T, for example, that isn't
appropriate for 10.4, or a .deb under 10.x that isn't usable at all on
10.y. It means that .deb for packages that are no longer appropriate
at all in a new dist will still be easily installable. We've had many
cases where a package gets out-of-sync (upgraded revisions) between
two dists and eventually wind up with the same revision but different
(sometimes *very* different) different dependencies and build options.
"Many cases"? Until now, this would clearly have been considered a bug.
We did revision jumps of 10 or now 1000 precisely to avoid this situation.
If your argument is going to become accepted Fink policy, then we should
really stop any "upgrade matrix" related activities and instead
concentrate on implementing the most painless way of doing
"remove /sw && install new Fink distribution && install the equivalent
of the old installed packages list".
--
Martin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
