symlinks in upstream and cvs-buildpackage
I trying to create a debian package for the MapServer project
(http://mapserver.gis.umn.edu/). I want to use cvs-buildpackage to track
my changes with CVS. cvs-inject does not allow there to be any symlinks
in the directory structure when importing the sources into CVS.
MapServer 3.5 unfortuneately has 3 symlinks. I thought I could just
remove them, and then in the debian/rules file have it recreate the
symlinks during the build-stamp target. This is all fine and dandy,
except that when I use `dpkg-source -b` to create the .diff.gz and .dsc
files, it reports:
pbaker@pbaker:~/mapserver-work$ dpkg-source -b mapserver-3.5
dpkg-source: building mapserver using existing mapserver_3.5.orig.tar.gz
dpkg-source: building mapserver in mapserver_3.5-1.diff.gz
dpkg-source: warning: ignoring deletion of symlink
mapscript/perl/mapscript.i
dpkg-source: warning: ignoring deletion of symlink
mapscript/python/mapscript.i
dpkg-source: warning: ignoring deletion of symlink mapscript/tcl/mapscript.i
dpkg-source: building mapserver in mapserver_3.5-1.dsc
Since dpkg-source ignores that I have removed the symlinks, when I later
do the `cvs-inject mapserver_3.5-1.dsc` it of course dies on the
symlinked files. I can use cvs-inject -F to have it remove the symlinks,
but I'm wondering what all this will break down the road. If you grab
the sources from my CVS repository you will get them without the
symlinks, but if you use the actual *unchanged*
mapserver_3.5.orig.tar.gz then it will have the symlinks. Does anyone
have any advice on how I should approach this? Thank you!!
P.S. assuming I get all this figured out, I'm going to be looking for a
upload sponsor and eventually an advocate. Any volunteers yet?
--Paul Baker
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-- Benjamin Franklin, 1759
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: