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

Bug#566269: Bug#566264: RM: libclass-dbi-loader-relationship-perl/oldstable -- RoQA; License problems



On Fri, Jan 22, 2010 at 04:27:47PM +0100, Patrick Schoenfeld wrote:
> Its kind of unfortune that this removal will remove other packages
> as well (and affect packages which do have users)
> but I think we simply *can not* keep the packages in any suite.

The module in question is a Perl 47 liners that only does some syntactic
"sugar" (I'd question even that) for DBI relationships.

>>> quote from documentation >>>
Now instead of saying

    BeerDB::Brewery->has_many(beers => "BeerDB::Beer");
    BeerDB::Beer->has_a(brewery => "BeerDB::Brewery");

    BeerDB::Handpump->has_a(beer => "BeerDB::Beer"); 
    BeerDB::Handpump->has_a(pub => "BeerDB::Pub");
    BeerDB::Pub->has_many(beers => [ BeerDB::Handpump => 'beer' ]);
    BeerDB::Beer->has_many(pubs => [ BeerDB::Handpump => 'pub' ]);


Just say

    $loader->relationship( "a brewery produces beers" );
    $loader->relationship( "a pub has beers on handpumps" );
>>> end quote >>>

We are distributing this thing since 2004.  Now you rush to remove it from
everywhere without caring about its reverse dependencies which would even
be easily fixable.  If someone had dropped a bomb upon us with this it
would've exploded some time ago already.

I won't rush to remove this from stable and oldstable just yet.  The timing
is a too unfortunate for this.  Let's replace the few relationships with
sane lines and not drop packages out of stable in a hurry (i.e. 3h between
bug filing and removal from unstable are weird).

If the ftpmasters choose to overrule me, so be it, but I encourage them
to look at the simplicity of the package and what it does first.  Yes,
there might be some regexps, but still.

> I've checked popcon for maypole and the package itself and they
> are below 100..

Not everyone believes^Wsubmits to popcon.

Kind regards,
Philipp Kern

Attachment: signature.asc
Description: Digital signature


Reply to: