Re: [lxml-dev] What are the equivalents of nowrite, nomkdir options
Hi Noah, Noah Slater wrote:
Noah, I'd be glad if you could test it and report back if it works as expected. I do not know if the directory creation business works now (i.e. if directories /are/ created).
Hi, sorry I can't test until I have a .deb package to install - so I am guessing I will have to wait until your changes arrive in Debian unstable.
That won't be before 1.0 then, I assume. It's actually not that hard to build Debian packages once they are part of Debian. Get the source .deb via apt and unpack it. Then you can replace the included lxml sources with the current SVN trunk (you may have to make a tgz from it), make sure the Debian package description has the version number you want and then rebuild it (IIRC, the command for that is "dpkg-rebuild" or something in that line). I don't have a Debian system to test, so I can't tell you what exactly you have to do. But there's an even simpler way. You can check out lxml from SVN and build it in-place in the source directory (see doc/build.txt on how to do that). To use it in your program, you can call Python like this: PYTHONPATH=/path/to/lxml-dir/src python myprogram.py To make sure it's the right version, use PYTHONPATH=/path/to/lxml-dir/src python -c \ 'import lxml.etree ; print lxml.etree.__version__' (the '/' makes it one line when you copy and paste it) Stefan
On 18.05.06 06:38:51, Stefan Behnel wrote:
Noah Slater wrote:
Noah, I'd be glad if you could test it and report back if it works as expected. I do not know if the directory creation business works now (i.e. if directories /are/ created).
Hi, sorry I can't test until I have a .deb package to install - so I am guessing I will have to wait until your changes arrive in Debian unstable.
That won't be before 1.0 then, I assume.
It's actually not that hard to build Debian packages once they are part of Debian. Get the source .deb via apt and unpack it. Then you can replace the included lxml sources with the current SVN trunk (you may have to make a tgz from it), make sure the Debian package description has the version number you want and then rebuild it (IIRC, the command for that is "dpkg-rebuild" or something in that line). I don't have a Debian system to test, so I can't tell you what exactly you have to do.
Let me jump in here. The procedure would roughly be: apt-get source lxml remove the unpacked directory tar.gz the trunk version and replace the orig.tar.gz that lies in the directory do dpkg -x lxml-...dsc and cd into the new directory dch -i and put a comment in there like "use trunk version", this will increase the debian version number so apt/dpkg don't get confused dpkg-buildpackage -rfakeroot -us -uc Eventually dpkg-buildpackage will tell you that some dependecies are missing, you can either install them manually or run apt-get build-dep lxml That'll give you deb's in the parent directory which can be installed using dpkg -i. I did this with trunk and s2-coder branch before 0.9 was released and it worked well. Andreas -- If your life was a horse, you'd have to shoot it.
Hi Andreas, Andreas Pakulat wrote:
On 18.05.06 06:38:51, Stefan Behnel wrote:
It's actually not that hard to build Debian packages once they are part of Debian. Get the source .deb via apt and unpack it. Then you can replace the included lxml sources with the current SVN trunk (you may have to make a tgz from it), make sure the Debian package description has the version number you want and then rebuild it (IIRC, the command for that is "dpkg-rebuild" or something in that line). I don't have a Debian system to test, so I can't tell you what exactly you have to do.
Let me jump in here. The procedure would roughly be:
apt-get source lxml remove the unpacked directory tar.gz the trunk version and replace the orig.tar.gz that lies in the directory do dpkg -x lxml-...dsc and cd into the new directory dch -i and put a comment in there like "use trunk version", this will increase the debian version number so apt/dpkg don't get confused dpkg-buildpackage -rfakeroot -us -uc
Eventually dpkg-buildpackage will tell you that some dependecies are missing, you can either install them manually or run apt-get build-dep lxml
That'll give you deb's in the parent directory which can be installed using dpkg -i.
I did this with trunk and s2-coder branch before 0.9 was released and it worked well.
Thanks for sharing that. I added a section for it in "doc/build.txt". Stefan
Yes, thank you. I shall experiment with this sometime over the next few days and let you know how I get on. Thanks, Noah On 5/18/06, Stefan Behnel <behnel_ml@gkec.informatik.tu-darmstadt.de> wrote:
Hi Andreas,
Andreas Pakulat wrote:
On 18.05.06 06:38:51, Stefan Behnel wrote:
It's actually not that hard to build Debian packages once they are part of Debian. Get the source .deb via apt and unpack it. Then you can replace the included lxml sources with the current SVN trunk (you may have to make a tgz from it), make sure the Debian package description has the version number you want and then rebuild it (IIRC, the command for that is "dpkg-rebuild" or something in that line). I don't have a Debian system to test, so I can't tell you what exactly you have to do.
Let me jump in here. The procedure would roughly be:
apt-get source lxml remove the unpacked directory tar.gz the trunk version and replace the orig.tar.gz that lies in the directory do dpkg -x lxml-...dsc and cd into the new directory dch -i and put a comment in there like "use trunk version", this will increase the debian version number so apt/dpkg don't get confused dpkg-buildpackage -rfakeroot -us -uc
Eventually dpkg-buildpackage will tell you that some dependecies are missing, you can either install them manually or run apt-get build-dep lxml
That'll give you deb's in the parent directory which can be installed using dpkg -i.
I did this with trunk and s2-coder branch before 0.9 was released and it worked well.
Thanks for sharing that. I added a section for it in "doc/build.txt".
Stefan
_______________________________________________ lxml-dev mailing list lxml-dev@codespeak.net http://codespeak.net/mailman/listinfo/lxml-dev
-- "Creativity can be a social contribution, but only in so far as society is free to use the results." - R. Stallman
participants (3)
-
Andreas Pakulat -
Noah Slater -
Stefan Behnel