On 23/12/11 18:49 +0100, Albert Cervera i Areny wrote:
> A Divendres, 23 de desembre de 2011 17:19:51, Cédric Krier va escriure:
> > On 23/12/11 16:39 +0100, Albert Cervera i Areny wrote:
> > > I think we need that compatibility/dependency to be in the module
> > > definition. So if the user installs the modules "purchase_shipment_cost"
> > > and "stock_account_ango_saxon", then
> > > "purchase_shipment_cost_anglo_saxon" should be automatically marked for
> > > installation as if it was a dependency.
> > 
> > So both module "purchase_shipment_cost" and "stock_account_ango_saxon"
> > need to know each other. There is no such option in distutils and from
> > my Gentoo packager experience, I never saw such dependencies.
> 
> Well, don't know about those, really. But Debian has an "incompatible" and 
> "suggested" options.

"incompatible" should never happen. If such things happen then it is all
the module that must be forbiden.

> Maybe something like "suggested" could be enough.

I find this Debian feature pointless because nobody understand what does
it mean. And more over as it is just suggested, I don't need to install
it.

> > > That
> > > information should probably come from the
> > > purchase_shipment_cost_anglo_saxon module, or it may come from any of
> > > the other two.
> > 
> > It can not because you can have the two modules without this one.
> 
> It depends on how you express that. It could be an in 
> "purchase_shipment_cost_anglo_saxon" that says: 
> 
> "required" if X and Y are installed.

It still need to be on both side. If the other one was not installed
when the first is, and you install it later than you don't get the
requirement.
Any way, I don't think conditional requirement is the solution. And I
never saw any package manager having such functionality.

And I really don't want to maintain such glue modules, I want to remove
them.

-- 
Cédric Krier

B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/

Attachment: pgpyuFMAG5KnV.pgp
Description: PGP signature

Reply via email to