On Thu, Dec 23, 2010 at 10:32:06AM +0100, c. wrote:
>
> On 22 Dec 2010, at 23:17, Søren Hauberg wrote:
>
> > ons, 22 12 2010 kl. 23:05 +0100, skrev Thomas Weber:
> >> Having quite some experience with maintaining the splitted packages in
> >> Debian I can assure you that maintaining the small packages in a
> >> distribution is at least *an order of magnitude* more work than the
> >> monolithic build ever was.
> >
> > Is there anything that can be changed in Octave-Forge that would
> > simplify this work?
>
> I vaguely remember David had implemented a method to automatically produce an
> RPM out of an OF package,
> maybe we could have something like
>
> pkg build -rpm package_name-version.tar.gz
>
> and
>
> pkg build -deb package_name-version.tar.gz
>
> directly in pkg.m?
I don't think that will work in the general case. I will probably work
for packages which contain only .m files (in fact I think that for a
bunch of .m files, pkg.m is overkill).
But for a package which compiles code, you have not much chance in
building something that will work across distributions.
Thomas
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
