Bug#311479: Nexuiz: status update?

[Bruno Kleinert]

This one time, at band camp, Alexander Schmehl wrote:
> Hi!
> 
> * Alexander Schmehl <tolimar at debian.org> [060627 22:09]:
> 
> > Difficult decission;  Depending on the answer to your next question, I
> > still think the best way would be:
> > - upload the -hotfix package
> >   - with both released hotfixes
> >   - with an conflict on the old -data
> >   - wait until it's through new
> > - upload a complete new -data package
> >   - without the first hotfix
> >     (Version will be changed; we'll need an eoch for that to work)
> >   - depend on -hotfix package
> 
> Other idea:
> - leave the first hotfix in the data package
> - create a the hotfix package with the second hotfix
> - upload a new revision of the -data package
>   - new -data depends on -hotfix
> 
> Pro:
> - save mirrors, users and everyone else to redownload -data
> - save us to use an epoch for -data
> 
> Cons:
> - ugly, since the hotfixes are seperated
> - ugly, since the -data has a version indicating the first hotfix
>   - that could confuse users
> 
> Other ideas?  Opinions?
> 
> 
> Yours sincerely,
>   Alexander
> 
> -- 
> http://www.netmeister.org/news/learn2quote.html
> http://www.catb.org/~esr/faqs/smart-questions.html

ok, here's my plan ;)

let's not touch any of the packages (yes, sounds wierd, BUT...)

i contacted upstream, they're about to release a bugfix release,
probably versionned like "2.0.1" or similar, around the next week.
when there's a new upstreasm version, all packages, especially
nexuiz-data, will be upgraded and there'll be no more hotfix files
around, which need to be packaged.

as nexuiz is not broken, in the sense of being unusable, i believe
there won't arrive much bug reports about the issues the second hotfix
is intended to solve. and if there arrive bug reports, we already know
the answer: just wait for the upstream bugfix release, it won't take
long.

this way, we don't get into the hotfix-packaging-hell. we'll never get
into trouble by newer -data packages conflicting with older -hotfix
packages. we can save confusing -hotfixes packages, confusing
dependencies and confusing meta-packages.

if ever such hotfix files will be released by upstream again,
i will NOT include them in the nexuiz packages, because the issues a
hotfix file should fix, never render the game unusable or unplayable.
also the hotfix files indicate there'll follow a bugfix release, soon.
and if it's really necessary to include updated game data, we can use
nightly snapshots from cvs, which automatically includes the fixes.

in short words: i learned my lessen about including files, which are
not part of any upstream release ;)

cheers - fuddl

-- 
Among elephants it's not considered cool nor in any good taste
to drain other elephants


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-games-devel/attachments/20060628/4c7bb753/signature.pgp