[Pkg-octave-devel] octave-pkg-dev_0.6.0_amd64.changes REJECTED
rafael at debian.org
Tue Sep 9 21:25:07 UTC 2008
* Joerg Jaspert <ftpmaster at debian.org> [2008-09-09 18:26]:
> rejected, for now.
> Why does this need a new package and can't go into an existing one?
I think you are talking about octave-pkg-rebuild, which is the new package
created from the octave-pkg-dev source. This package is intended to be a
dependency for all packages providing Octave add-ons (as the Octave Forge
I decided to create a separate package for it in order to avoid pulling
unnecessary dependencies. Had I included the octave-pkg-rebuild into
octave-pkg-dev, the octave3.0-headers package would become also a
dependency, pulling several unnecessary lib*-dev packages at install time.
If you have any suggestion about another way of doing this, I would love to
hear from you. Better, join the discussion in the thread in
pkg-octave-devel . BTW, Thomas Weber already suggested to include the
functionality of octave-pkg-rebuild into octave3.0 and I explained why I
think this is not a good idea.
Please note that octave-pkg-dev is a Debian native package and we use it to
help building/installing the several octave-* packages, so that the Debian
Octave Group should have some authority to decide what is better for package
the Octave-related stuff.
If I do not hear from you soon and if there is consensus in the
pkg-octave-devel mailing list around this issue, I will reupload the
More information about the Pkg-octave-devel