Hi Anton, there is some misunderstanding on how packages should be named. I had the following scenario in mind:
1. Each yade version (release or snapshot) has a different package *name* -- that makes it possible to install all version at once, otherwise the newer package will upgrade the older one. That means that the version is embedded in the package name. PLEASE no yade-bzr package, that breaks this scenario. Instead, yade-bzr1234 etc, which provides yade-snapshot (the "snapshot" is consistent with the system used in debian, e.g. gcc-snapshot etc). IIRC the scripts/debian-prep script was trying to do it this way. What it currently does wrong is to get the right *version* number (it uses 1~distribution1 or such in all cases), which should be the same as the one embedded in the name, plus updates etc: e.g. yade-0.50 would have version 0.50.0~lucid1 etc, where lucid1, lucid2 and so on should correspond to packaging changes, while 0.50.0, 0.50.1 etc to "upstream" changes in the code itself (update releases). For snapshot packages, there should be some deliberation. 2. Snapshot packages provide yade-snapshot *virtual* package; in such case, installing yade-snapshot will drag in the latest non-virtual package. Release package provide yade *virtual* package. Maybe you have some better reasons in mind, but please explain where are you heading. Looking back at the e-mail, I might create a wiki page for that ;-) Needless to say, your packaging effors are greatly appreciated. Cheers, Vaclav -- Vaclav Smilauer <[email protected]> _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
