[Kolab-devel] [issue1035] Some packages questions, such as perl vendorlib and tar.bz2 vs tar.gz

[Richard Bos]

New submission from Richard Bos <radoeka at xs4all.nl>:

Bernhard,    
    
is it okay that only tar.bz2 files are created?  At the moment 2 tarbals are  
created (.gz and bz2).  If  [no-dist-gzip] is added to configure.ac, like;    
+AM_INIT_AUTOMAKE([gnu] [1.7] [dist-bzip2] [no-dist-gzip])     
only 1 is created. 
 
Another thing: it is possible to determine the paths to program using configure  
this however requires that the concerning packages are actually installed.  
This makes sense of course, when a user installs the package on his/her system,  
but as packages that might not be the case...  
  
By adding the code below to kolabd/configure.ac, the right paths for bash,   
perl and php are determined by configure for as well as the openpkg  
distribution as for other distributions.  
  
+if test x"$openpkg" = x"true"; then     
+       PATH=/kolab/bin:/kolab/lib/openpkg:$PATH     
+fi     
+     
+# Don't use BASH as variable as that is already set by bash itself and     
+# is not overwritten...     
+AC_PATH_PROG(BASHELL,[bash])     
+if test -z "$BASHELL"; then     
+   AC_MSG_ERROR([bash not found])     
+fi     
+     
+AC_PATH_PROG(PHP,[php])     
+if test -z "$PHP"; then     
+   AC_MSG_ERROR([php not found])     
+fi     
  
This is nice for bash and php, but these are rather fixed on most distributions  
and using dist_conf/* for this would be fine to, too.  However, for perl it is 
very  
usefull as the perl vendorlib location is different from dist to dist and even  
for different versions of the same distribution.  The perl vendorlib can be  
determined with:  
     
+AC_PATH_PROG(PERL,[perl])     
+if test -z "$PERL"; then     
+   AC_MSG_ERROR([perl not found])     
+fi     
+     
+AC_MSG_CHECKING([perl vendor lib])     
+perllib=$($PERL -V:vendorlib | sed "s/.*'\(.*\)'\;/\1/")     
+AC_SUBST(perllib)     
+AC_MSG_RESULT($perllib)     
  
  
So the question is:  
- is it okay to determine perl and perl vendorlib using configure (requires  
  perl to be installed on the packager system  
- is it okay to determine bash and php too using configure (though this is not  
  very important)  
  
 
Is it okay that I used 'make clean dist' to 'make clean distcheck' in 
./kolab-webadmin/Makefile ./kolabd/Makefile ./kolab-resource-handlers/Makefile 
 
The advantages is that the make distcheck, checks that the code can actually 
be build using the Makefile, as the user would do.  It takes a little more 
time to package, but it ensures quality :)

----------
assignedto: bernhard
messages: 6090
nosy: bernhard, martin, mhuewe, rbos
priority: wish
status: unread
title: Some packages questions, such as perl vendorlib and tar.bz2 vs tar.gz
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1035>
________________________________________________