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

Re: RE : RE : cctbx debian package

On Mon, 23. Jul 19:04, Frédéric-Emmanuel Picca wrote:
> if I remember correctly the install target is the one which create the symlinks with autotools.
> A good reason to stick with the autotools. Everything comes together for free :).
> But hey peoples think that theses brand new build systems are sexy...
I know I'd prefer autotools too. Scons is not so bad too. It has some good ideas
but it's a long way to become a drop in replacement for autotools. Maybe in a
few years it'll be ready. I was searching for shlib versioning and people are
complaining about it since 2008 and also sended patches upstream but nothing
changed since.
> > Just found out that scons builtin Install() command does not install symlinks
> > but it follows them. So again I have to rip that all apart and probably utilize
> > libtool for Install() again.
> This is why in my first post I was interested by a Makefile.am generator using the introspection of their build system :)
> Good luck and once again thanks for your efforts.
Could have been a good choice back then but I'm at this point where I put so much effort
into Scons and read so much source code that I don't want to give it up. And to
be honest I have way more experience in python then anything else.

But I solved the problem with the symlinks. I created LibtoolInstall() Builder.
I guess when I'm finished with all I'm gonna have to contribute my libtool
builders to the scons community.

Some other questions. There are packages like libscitbx0 where I put
libscitbx.so and libscitbx_boost_python-py**.so in it. I saw the lintian complains and
I wonder if I should pack them seperately. Meaning:

I was also thinking about the dispatcher scripts. Most of them seem useless to
me. All scripts ending *.python are just calling the interpreter with the proper
pythonpaths what is useless. The other scripts especially boost.* cbflib.* etc would just
pollute the namespace in /usr/bin. People could be confused. We could put them
in a seperate package and don't put the files into /usr/bin but for example
/usr/share/cctbx/bin. What is your opinion on that?


Reply to: