[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: zynaddsubfx 2.2.1 should make it into sarge...



Hi Eduardo,

On Wed, May 04, 2005 at 01:50:47PM -0300, Eduardo Marcel Macan wrote:
> Good news we're now frozen :D, but it seems that one of my packages 
> didn't make it on time for the freeze:

> http://packages.qa.debian.org/z/zynaddsubfx.html

> zynaddsubfx 1.4.3  (the version in testing) is way too old, I wish any 
> of the 2.x series package had made it,
> Not only because 1.4.3 is very old and lacks a lot of functionality when 
> compared to 2.x  but mainly because
> the data format used to store program state and data has changed from a 
> binary format to a xml-like text
> file, which solves lots of potential edianess problems when using binary 
> data in different platforms (never had
> the chance to really test for those) than the one in which the file was 
> saved. And also because there's no tool available
> to convert between the old and the new data formats.

> Our users will have problems to exchange data files ( musical instrument 
> definitions, this is a synthesizer) among
> other users of this software because of the different format, and will 
> accumulate data that will need to be converted
> someday in the future, using tools that will have to be developed 
> specially for this case. In the end it will
> will require much more work (for both us and the user) and will deliver 
> much less value (now I did sound
> corporate eh?).

I'm afraid I'm not really convinced that this alone is enough reason to
introduce a major new upstream release of the package at this stage of the
release cycle.  I'm sorry if having 1.4.3-1.1 in sarge would cause you more
work in the long term; you do have the option as the maintainer to ask for
its removal from the release, if you think it shouldn't be shipped in this
state.

I might have viewed the situation differently if this new upstream version
had only been waiting for arm (which is still is, until the mxml binaries
are signed and uploaded by the buildd admin), but the additional upload of
2.2.1-1 two days ago means that this package is still undergoing too many
changes for me to be willing to let it in.

-- 
Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature


Reply to: