[Pkg-octave-devel] The "no octave-forge package" discussion

Thomas Weber thomas.weber.mail at gmail.com
Thu Nov 8 18:47:22 UTC 2007


Am Donnerstag, den 08.11.2007, 11:34 -0600 schrieb Jordi Gutiérrez
Hermoso:
> Uh, I'm having a hard time understanding what's going on with the
> 'forge packages and why it was decided to not make a Debian package
> out of them. Could I get a quick summary or a link to one, please?

The answers to your questions are simply: 'nothing' and 'time' (although
the second one is a bit misleading).

There's currently nothing going on regarding octave-forge and the reason
for that is time, or lack thereof[1]. There's no formal decision one way
or another. Be invited to submit a framework for creating these
packages. A framework is needed: we are talking about 40+ packages,
every single one needing an upload for every API change in Octave; well,
more precisely every package which creates .oct files must be rebuilt
for every API-changing Octave version (which currently means every 2.9
snapshot). Be advised that we have exactly *one* person that can build
and upload these packages.

A few guidelines: the build process must not write to /home (one of the
mips buildds will detect this, so if you forget it, you will be
reminded ;) ). Packages must have a working clean target or Lucas
Nussbuam will send you an RC bug (he rebuilds the archive once in a
while). And probably a dozen other things that lintian will tell you.

	Thomas






More information about the Pkg-octave-devel mailing list