On Oct 30, 2005, at 11:56 AM, Simon Waters wrote:
Jos I. Boumans wrote:
Currently we're prototyping it -- and we only have one build box,
churns out i386 packages on unstable... I'm not sure however that
grabbing bleading edge software from CPAN and building it on debian
stable should warrant it being marked 'stable' -- or am i not
understanding what you mean?
I assume he means "built for stable", as this might include different
dependencies for none Perl code (i.e. C libraries).
The current build engine only does perl only modules, as detecting
(and satisfying) non perl requirements is far from trivial and falls
outside the 80/20 mark we're aiming at.
Snipping this long post for convenience, I'll just make a few general
about what we're aiming at, in the hope this answers a lot of your
* debian.pkgs.cpan.org is a mirror for debian packages which were
from their CPAN counterparts, for the express purpose of not having
files on your debian
system that dpkg is not aware of, and easing the install/upgrade path.
This is by /no means/ a replacement for debian's perl archive.
* CPANPLUS::Dist::Deb is the plugin into CPANPLUS that makes this
possible. It can do
a lot more than just create above packages. You could have a non-perl
hooked in, you can put packages in a stable namespace, you can make
packages *just* like
they would come from debian (mainly intended for debian developers).
* we are not looking to offer any more services than the above, but
hope that the toolkit
provides enough functionality for other interested parties to provide
the services they
feel are lacking.
If that last statement is something you can work with to realise the
things you're proposing,
we'll of course be more than happy to assist on matters of the toolkit.
I hope this answers your questions,
"Whenever you find you are on the side of the majority,
it is time to pause and reflect." - Mark Twain