[debian-mysql] community/enterprise naming split idea
seanius at debian.org
Tue Dec 18 18:02:46 UTC 2007
On Tuesday 18 December 2007 03:21:57 pm Monty Taylor wrote:
> I stuck it in a branch called community so you could check it out and
> give me feedback. It will not hurt my feelings if you think it's a bad
> idea in general. However, I would like to do something with provides so
> that not only can people who buy enterprise "upgrade" from community,
> but also if they decide they didn't like the enterprise packages, I'd
> like for them to be able to do the other way, too.
just to weigh in with my 0.02 $currency, i'd like to say that I dislike the
idea of anything that involves changing the names of the packages to
include "community". for me it's something akin to salt on an open sore.
however, that said i do support the notion of being able to support going back
and forth between the two versions. but wouldn't that be possible with some
added Provides/Conflicts/Replaces? i.e. the mysql official packages could
and vice versa for debian. i don't have the time/interest to check this
myself, but i imagine this (or something similar) would work without needing
to add additional metapackages or change package names.
sean (who's mostly armchair maintaining currently, fwiw)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20071218/2f9a0695/attachment.pgp
More information about the pkg-mysql-maint