>>: Faré >: janderson >> Daniel, if you want changes only every 5 to 10 years, do like >> janderson: try an upgrade every 5 years, find that it breaks your code >> somehow and downgrade back to the old version without further >> investigation. Then maybe 10 years from now you'll get the system >> dependency bug fixed. > > if one wishes to ascribe expectations to my actions, allow me to correct the > presumption, as more accurate would be the hope, in ten years to have the > luxury to work with a build system which leaves my dependency descriptions > alone and uses them to do what it should, without failing for unrelated > reasons. > Well, after 5 to 10 years, some amount of bitrot is to be expected, especially for software that wasn't abandoned but saw active development.
It is very unfair of you to complain without ever submitting a bug report: we get no chance to defend ourselves. Did we do something stupid? Did you? Was the issue a known backward incompatibility? Was there a trivial fix, whether already documented or not yet? We'll never know. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You can of course keep using any old ASDF 1 you like, or whichever or even MK-DEFSYSTEM, which is quite stable. Only if you ever want to use recent libraries that depend on new ASDF features or bug fixes, will you have to upgrade your ASDF.
