Why are we including what appears to be a MacOSX binary for GNU make
in CVS (gem/skeleton/macosx/bin/make)? We wouldn't normally store
binary executables in CVS.
Apart from anything else, this obligates us to either host the source
code for that version of make, or offer to provide the source code
upon request for three years from the time that the binary is no
longer available via CVS. Do we even know which version of the source
code we need to supply?
--
Glynn Clements <glynn@gclements.plus.com>
Oops, that's a leftover from pre-CVS development of GEM.
Just delete it if you want.
Binary make versions were planned for deploying pre-compiled extension
modules on systems that don't have C development tools installed.
Benjamin
Glynn Clements wrote:
Why are we including what appears to be a MacOSX binary for GNU make
in CVS (gem/skeleton/macosx/bin/make)? We wouldn't normally store
binary executables in CVS.
Apart from anything else, this obligates us to either host the source
code for that version of make, or offer to provide the source code
upon request for three years from the time that the binary is no
longer available via CVS. Do we even know which version of the source
code we need to supply?
--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany
Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg
Benjamin Ducke wrote:
> Why are we including what appears to be a MacOSX binary for GNU make
> in CVS (gem/skeleton/macosx/bin/make)? We wouldn't normally store
> binary executables in CVS.
>
> Apart from anything else, this obligates us to either host the source
> code for that version of make, or offer to provide the source code
> upon request for three years from the time that the binary is no
> longer available via CVS. Do we even know which version of the source
> code we need to supply?
Oops, that's a leftover from pre-CVS development of GEM.
Just delete it if you want.
Unfortunately, "cvs remove" won't suffice, because the file will still
be available from CVS using an explicit revision.
We either need to add the corresponding source code to CVS (a tarball
would suffice, but it needs to be the correct version), or have
someone manually remove the ,v file from the repository.
--
Glynn Clements <glynn@gclements.plus.com>
Hi Bernhard,
as CVS admin, could you help us with this problem before it
becomes too messy?
thanks,
Markus
On Tue, Jan 23, 2007 at 07:04:23PM +0000, Glynn Clements wrote:
Benjamin Ducke wrote:
> > Why are we including what appears to be a MacOSX binary for GNU make
> > in CVS (gem/skeleton/macosx/bin/make)? We wouldn't normally store
> > binary executables in CVS.
> >
> > Apart from anything else, this obligates us to either host the source
> > code for that version of make, or offer to provide the source code
> > upon request for three years from the time that the binary is no
> > longer available via CVS. Do we even know which version of the source
> > code we need to supply?
>
> Oops, that's a leftover from pre-CVS development of GEM.
> Just delete it if you want.
Unfortunately, "cvs remove" won't suffice, because the file will still
be available from CVS using an explicit revision.
We either need to add the corresponding source code to CVS (a tarball
would suffice, but it needs to be the correct version), or have
someone manually remove the ,v file from the repository.
--
Glynn Clements <glynn@gclements.plus.com>
_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev
Hi,
On Wednesday 24 January 2007 00:32, Markus Neteler wrote:
as CVS admin, could you help us with this problem before it
becomes too messy?
sure...
On Tue, Jan 23, 2007 at 07:04:23PM +0000, Glynn Clements wrote:
> Benjamin Ducke wrote:
> > > Why are we including what appears to be a MacOSX binary for GNU make
> > > in CVS (gem/skeleton/macosx/bin/make)? We wouldn't normally store
> > > binary executables in CVS.
> > Oops, that's a leftover from pre-CVS development of GEM.
> > Just delete it if you want.
>
> Unfortunately, "cvs remove" won't suffice, because the file will still
> be available from CVS using an explicit revision.
>
> We either need to add the corresponding source code to CVS (a tarball
> would suffice, but it needs to be the correct version), or have
> someone manually remove the ,v file from the repository.
removed directory gem/skeleton/macosx from the repository.
Bernhard