[Pkg-octave-devel] New potential packager

Juan Pablo Carbajal carbajal at ifi.uzh.ch
Mon Feb 20 19:12:19 UTC 2012

Hi all,

I am learning how to do packages for Debian. My initial objective was
to help speeding up the packaging of octave versions but apparently
that is kind of "covered". So it seems I will help packaging Octave
forge packages that needs to be packaged.

In this regards I have the following question. Is it needed that all
Octave Forge (OF) are packaged? I mean I see in the wiki lots of
complaints and warnings about packages that are only a bunch of
m-files and those could be managed within Octave easily without extra
burden to this group.
Is it sensible to categorize packages in relation to their dependency
on external libraries? Like stand-alone (which wouldn't require a
Debian package) and "dependent" (or something of that sort) for the
ones that depend on externals library and require a more exhaustive
dependency control?

I am a rookie, so be indulgent if my opinion is too naive. But I
thought maybe this would speed up the process and keep the efforts

Thank you!

M. Sc. Juan Pablo Carbajal
PhD Student
University of Zürich

More information about the Pkg-octave-devel mailing list