packaging a lib which needs to be compiled in different ways for different users

[Hugo Cisneiros]

On Wednesday 05 July 2006 17:00, Hans de Goede wrote:
> >> Does not following this rule sound reasonable / any objections?
> >
> > Would it make sense to have ode-opcode, demo-effects-opcode,
> > crystal-space-opcode etc packages?  That is, split the opcode part
> > into a seperate subpackage that does not require the main package, and
> > if one project can use another's opcode it can do so?
>
> Erm, no I think the effort needed to make that work is not worth the gain.

+1

> Regards,
> Hans

-- 
[]'s
Eitch

http://www.devin.com.br/eitch/
"Talk is cheap. Show me the code." - Linus Torvalds