Hi!
Do I need to download svn trunk, if I want to test the prereleases?
For the debian packaging I think the debian/control file missed a ',' character in it. So I attached a really minor patch(lol). cd debian; svn diff -x -u >control.diff
I think the version from '0.43+0.44pre1-1' should changed to something '0.44pre1-1'. Am I wrong?
However Im not able to build from inkscape svn. From the svn snapshot tarballs compiles fine. What is need to running in the fresh svn checkout, to be identic to the svn snapshot tarballs? Im talking about this tarball: http://inkscape.modevia.com/svn-snap/inkscape-20060524-0300.tar.bz2
From fresh checkout I got this error message: DEB_BUILD_OPTIONS="nostrip noopt" dpkg-buildpackage -rfakeroot -uc -b
dh_clean debian/rules build make: *** No rule to make target `configure', needed by `builddir/config.status'. Stop.
If I copy the 'configure' file, I got this: cd builddir \ && CFLAGS="-g -O0" CXXFLAGS="-g -O0" \ ../configure --host=i486-linux-gnu --build=i486-linux-gnu \ --prefix=/usr --mandir=${prefix}/share/man --infodir=\ ${prefix}/share/info configure: error: cannot find install-sh or install.sh in .. ../.. ../../.. make: *** [builddir/config.status] Error 1
So I think it some auto tool here.
Can somebody help me a little?
Khiraly
Hi Khiraly, On Wed, May 24, 2006 at 12:40:34PM +0200, Khiraly wrote:
Hi!
Do I need to download svn trunk, if I want to test the prereleases?
For the debian packaging I think the debian/control file missed a ',' character in it. So I attached a really minor patch(lol). cd debian; svn diff -x -u >control.diff
I think the version from '0.43+0.44pre1-1' should changed to something '0.44pre1-1'. Am I wrong?
The problem is that apt/dpkg thinks 0.44pre1 is larger (= newer) than 0.44-1. This means that if you create a package version 0.44pre1 the update to the later released version 0.44 will not work automatically. Best practice for home-built packages is to generate packages not versioned -1... but -0.1... to ensure the update to (later) official packages.
However Im not able to build from inkscape svn. From the svn snapshot tarballs compiles fine. What is need to running in the fresh svn checkout, to be identic to the svn snapshot tarballs? Im talking about this tarball: http://inkscape.modevia.com/svn-snap/inkscape-20060524-0300.tar.bz2
You need to run ./autogen.sh in a fresh svn-checkout. This will generate the needed configure script.
HTH,
Wolfi
On Wed, May 24, 2006 at 12:40:34PM +0200, Khiraly wrote:
Hi!
Do I need to download svn trunk, if I want to test the prereleases?
No, when we do pre-releases we are explicit about both tagging svn and producing a tarball, as well as announcing it, so there should be no confusion.
The key thing right now is getting inkscape back to being able to pass make distcheck; after that, expect to start seeing pre-releases produced and announced.
For the debian packaging I think the debian/control file missed a ',' character in it. So I attached a really minor patch(lol). cd debian; svn diff -x -u >control.diff
I think the version from '0.43+0.44pre1-1' should changed to something '0.44pre1-1'. Am I wrong?
However Im not able to build from inkscape svn. From the svn snapshot tarballs compiles fine. What is need to running in the fresh svn checkout, to be identic to the svn snapshot tarballs? Im talking about this tarball: http://inkscape.modevia.com/svn-snap/inkscape-20060524-0300.tar.bz2
From fresh checkout I got this error message: DEB_BUILD_OPTIONS="nostrip noopt" dpkg-buildpackage -rfakeroot -uc -b
dh_clean debian/rules build make: *** No rule to make target `configure', needed by `builddir/config.status'. Stop.
Run the ./autogen.sh script to create the configure script. Sorry for the extra step, but this is normal for autopackage. Since configure is a generated script, we don't keep it in SVN, but instead generate it during the packaging process.
If I copy the 'configure' file, I got this: cd builddir \ && CFLAGS="-g -O0" CXXFLAGS="-g -O0" \ ../configure --host=i486-linux-gnu --build=i486-linux-gnu \ --prefix=/usr --mandir=${prefix}/share/man --infodir=\ ${prefix}/share/info configure: error: cannot find install-sh or install.sh in .. ../.. ../../.. make: *** [builddir/config.status] Error 1
So I think it some auto tool here.
My guess is autogen.sh creates that script as well. Give it a shot.
Bryce
participants (3)
-
Bryce Harrington -
Khiraly -
Wolfram Quester