Re: Should lambda-align v2 replace v1 or be its own Debian package?
Hi Michael,
On Mon, Jan 14, 2019 at 10:25:55AM +0200, Michael Crusoe wrote:
> Currently we package v 1.0.3, last stable release of Debian had v1.0.1
> <https://packages.debian.org/search?searchon=sourcenames&keywords=lambda-align>
> ,
>
> https://github.com/seqan/lambda/releases/tag/lambda-v2.0.0
> https://github.com/seqan/lambda/wiki/LAMBDA-%E2%86%92-lambda2-guide
>
> The CLI has significant changes:
>
> Lambda1 had two executables: lambda and lambda_indexer
> > Lambda2 has a single executable: lambda2
> >
> > lambda2 has different sub-commands
> >
>
> The on disk format has changes:
>
> Lambda now stores it's index files in a separate folder instead of
> > cluttering the directory where your original .fasta file was. These folders
> > have a .lambda extension, but are regular folders that just contain the
> > different data files needed.
> >
>
> There doesn't appear to be an auto-upgrader or shim script provided for
> lambda v1 users.
>
> However, there are no references from other Debian packages to
> lambda-align's binaries, so upgrading to v2 without changing the package
> name won't break any packages, but it will break user scripts.
>From a plain Debian point of view adding a file debian/NEWS.Debian
explaining the issue will show the change in the new version. From a
user perspective it might be interesting to have the old version as
well. If you volunteer to maintain the old version as lambda-align1
some users might be happy. Unfortunately its an extremely rare
event that those users show up here on this list and express their
interest about this (despite this list was explicitely created for
communication with our users).
Hope these thoughts will enable you to draw a sensible decision
Andreas.
PS: In any case I'd stick with the lambda-align package name for the
new version. Otherwise we might need to wait for ftpmaster
acceptance until after freeze and thus the latest version will
not make it into Buster.
--
http://fam-tille.de
Reply to: