[GRASS5] [[GRASSLIST:3732] RE: Grass 5.0.0pre4 RPMs for Mandrake 8.2]

GRASS GRASS developer
,
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I was told this mail would be more appropriate for the devel list
than the grasslist, so here goes ...

In case you are missing the context, I have put grass 5.0pre3 RPMs into
the Mandrake Cooker, and am busy with pre4 RPMs, which can be found at:

http://ranger.dnsalias.com/mandrake/mandrake8.2/grass/

At the moment, only one RPM is built, with gdal,postgresql and nviz
support, subpackages may com in the future.

Markus Neteler wrote:
| Note: Lapack/Blas is not needed by GRASS. It is implemented for future
| extensions.
|

I have a patch against pre4 that I am using in the RPM, which makes life
quite a bit easier when packaging. It adds a new shell variable DESTDIR
to the Makefile.in, which indicates where the software's 'chroot' should
be during installation, so that during packaging, packagers

1)don't need to be root
2)don't mess with system files
3)don't need to reset 20 variables for make (prefix etc)

There may still be some issues with it (I don't know if it's possible to
get gmake5 and gmakelinks5 to work anyway, but they currently get the
path to the RPM_BUILD_ROOT).

The use of this patch allows packagers to do make
DESTDIR=$RPM_BUILD_ROOT INST_DIR=/usr/lib/

Mandrake even has a macro which implements this, so I actually use:
%makeinstall_std INST_DIR=%{_libdir}/grass5

I would appreciate if someone who builds grass often could test a normal
build without supplying DESTDIR to ensure it doesn't break things, and
then maybe it could be considered for the original source?

Please see the attached patch.

Regards,
Buchan

- --
|----------------Registered Linux User #182071-----------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE88j1zrJK6UGDSBKcRAvCHAJwMSt9E8UldjALsj+UDPxDp7R7wBACcDNaP
Bui5mI+GzUl2MrVpgFithxE=
=79G1
-----END PGP SIGNATURE-----

(attachments)

grass5_makefile_destdir.patch (15.2 KB)

2

On Mon, May 27, 2002 at 04:06:43PM +0200, Buchan Milne wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

OK, I was told this mail would be more appropriate for the devel list
than the grasslist, so here goes ...

In case you are missing the context, I have put grass 5.0pre3 RPMs into
the Mandrake Cooker, and am busy with pre4 RPMs, which can be found at:

http://ranger.dnsalias.com/mandrake/mandrake8.2/grass/

Have you compared them to the RPMs from the FreeGIS CD?
It'*s probably fine to have more than one spec file.

3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bernhard Reiter wrote:
| On Mon, May 27, 2002 at 04:06:43PM +0200, Buchan Milne wrote:
|
|>-----BEGIN PGP SIGNED MESSAGE-----
|>Hash: SHA1
|>
|>OK, I was told this mail would be more appropriate for the devel list
|>than the grasslist, so here goes ...
|>
|>In case you are missing the context, I have put grass 5.0pre3 RPMs into
|>the Mandrake Cooker, and am busy with pre4 RPMs, which can be found at:
|>
|>http://ranger.dnsalias.com/mandrake/mandrake8.2/grass/
|
| Have you compared them to the RPMs from the FreeGIS CD?
| It'*s probably fine to have more than one spec file.

I have looked at the spec file in the grass source (under rpmspecs), but
there were quite a few things that needed to be changed for inclusion in
Mandrake, and olny 160 of 3800 lines weren't %files lists (which I hope
to be able to do with %files -f <filename> and some sed/grep).

I have some experience building RPMs on multiple releases of Mandrake (I
help maintain samba for Mandrake) with optional features, and I would be
prepared to help getting one SPEC file that builds correctly (both in
terms of functionality and and compliance with building standards for
the distro). The patch mentioned would be a good first step in that
direction, IMHO.

Regards,
Buchan

- --
|----------------Registered Linux User #182071-----------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE88kEYrJK6UGDSBKcRAuQEAJ9/HapcQdK8YjrpANylJToNtBwNigCfXZUd
5AZ4G4dEzPFzgb/P9i9Q+WI=
=zIMj
-----END PGP SIGNATURE-----