[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: building own package



Hi,

On Wed, Aug 03, 2005 at 11:21:35AM +0200, Tomas Davidek wrote:

> * I store all the scripts in a tarball, so all I have to do is to unpack 
> them in the respective directory during the "make install" stage (i.e. 
> no compilation is needed). I succeeded to do so by introducing  the 
> following Makefile:
> -------------
> clean:
>        rm -fr debian/ucjf-security
> 
> install:
>        cd $(DESTDIR) ; \
>        tar -xvzf ../../../ucjf-security_1.0.1.orig.tar.gz     
> --------------
> It works, however I would expect that the path to a tarball can be 
> specified in a better way (is there any variable containing the top 
> directory name ?). Also, the version should not be hardcoded there, I 
> guess. Is there a way to tell the Makefile to use the latest 
> version/same version as is the name of the working directory ?

if the debian/rules file is executed then the orig tarball is already
unpacked (with the diff applied if it isn't a native package). Why
untar again? Just place the files with "cp" where you want them
to be.

> * since the pakcage contains only few shell scripts, it should be 
> architecture-independent. Therefore, I specified "Architecture: any" in 
> the "control" file and also moved all the action in the "rules" file 
> into the binary-indep section (see attachment).... However, the 
> resulting package still contains in its control file the item 
> "Architecture: i386" (which is where the package is produced, but ....).

this should be "Architecture: all", not any.

-Ralf.
-- 



Reply to: