On Wed, Apr 20, 2011 at 07:13:40AM +0100, Andy Buckle wrote:
> On Wed, Apr 20, 2011 at 12:56 AM, Stephen Montgomery-Smith
> <step...@missouri.edu> wrote:
> > So when a new package is rolled out, for example bim-1.0.1.tar.gz, when
> > you untar it, it is unpredictable whether the directory created is
> > called "bim" or "bim-1.0.1." Some packages use the former name
> > convention, some packages use the latter.
> >
> > As the FreeBSD maintainer of the octave-forge-* ports, this
> > unpredictability can be frustrating. Can we decide from now on to stick
> > to one convention or the other?
> >
> > Thanks, Stephen
>
> I think it is clear from this
>
> http://octave.sourceforge.net/developers.html
>
> that the directory should not include the version number. Perhaps that
> page could be tweaked to make it clearer.
This page may suggest this, but I consider it a very bad idea for
several reasons:
1) In order to find out which version of a package you have, you need to
extract it first; that is, after you have downloaded it, which you must
*again* do just to find out which version it is. Just imagine Octave
using such a scheme - one octave.tar.gz to rule them all.
2) Obviously, the extraction of such package will happily overwrite
earlier versions of the same package in the same directory.
3) pkg.m currently appends the version to the name of the package when
installing it.
Thomas
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
