[Mailman-Developers] mailman / archive-ui / licensing questions

Toshio Kuratomi a.badger at gmail.com
Wed Apr 4 06:55:54 CEST 2012


On Wed, Apr 04, 2012 at 11:41:42AM +0800, Paul Wise wrote:
> On Wed, Apr 4, 2012 at 11:21 AM, Bob Puff wrote:
> 
> > I think the majority of MM users will be simply using the RPM that comes with
> > their distro, and there is a real benefit to stuff working right "out of the
> > box".  This includes the Archiving functions.
> >
> > Its great to have options, and giving a list of possible alternatives for
> > users is excellent, but I think releasing MM 3 without -any- archiver is a
> > down-grade from the current MM 2.x.
> 
> In the Debian world we would do something like this:
> 
> Package: mailman3
> Depends: mailman3-archiver-default | mailman3-archiver
> 
> Package: mailman3-archiver-default
> Depends: mailman3-archiver-hyperkitty
> 
> Package: mailman3-archiver-hyperkitty
> Provides: mailman3-archiver
> 
> Is something like that not possible in the RPM world?
> 
Not sure what the | syntax is so it may not be.  But what we might do would
be have a virtual provide.

Package mailman3
Requires: mailman3-archiver

Package: mailman3-archiver-hyperkitty
Provides: mailman3-archiver

Package: mailman3-archiver-pipermail-eeewwww
Provides: mailman3-archiver

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-developers/attachments/20120403/03f2dd72/attachment.pgp>


More information about the Mailman-Developers mailing list