Hey y'all,

I'm disappointed to discover that the lazarus are now requiring libatk 1.29.3 (or greater) whereas debian stable has 1.22

What's the status on this? Is there any chance that this requirement might be relaxed in the future?

I tried installing lazarus-ide-qt, but the lazarus-ide package still seems to have a bunch of gtk requirements. Perhaps the lazarus-ide package needs to be cleaned up?

Maybe I need to start using svn now, in order to avoid some of these library dependencies?

Thanks,
David.

Hey y'all, I'm disappointed to discover that the lazarus are now requiring libatk 1.29.3 (or greater) whereas debian stable has 1.22

AFAIK the libatk dependency is automatically setup by the dpkg tool using the version of the building machine.

What's the status on this? Is there any chance that this requirement might be relaxed in the future?

I guess not, except we downgrade the debian machine.

I tried installing lazarus-ide-qt, but the lazarus-ide package still seems to have a bunch of gtk requirements. Perhaps the lazarus-ide package needs to be cleaned up?

I didn't check. It should not have any gtk requirements.

Maybe I need to start using svn now, in order to avoid some of these library dependencies?

Yes, it is worth a try.

Mattias

I'm disappointed to discover that the lazarus are now requiring libatk 1.29.3 (or greater) whereas debian stable has 1.22

The same for the official rpm's, with dependencies that I cannot fulfill on my 3 year old system.

Maybe I need to start using svn now, in order to avoid some of these library dependencies?

I'd suggest to use an stable branch, the trunk currently is in an horrible state :-(

DoDi

Hi

2010/4/7 Mattias Gaertner :

I think this is a bad idea. Forcing Debian users to install Testing/Unstable is a bad idea.

Debian Stable exists for a reason, a very good reason, far beyond any Lazarus reason to depend on Debian Testing/Unstable.

Gustavo

I asked on oftc's #debian-devel and the advice was to "use pbuilder and set up a different environment there to build inside."

It sounds like the deb creation process could use some refinement. I don't have much experience here but would be happy to do some research and see if I can assist in the process.

I see there is a creation script here:
http://svn.freepascal.org/svn/lazarus/trunk/tools/install/create_lazarus_deb.sh

Vincent previously mentioned he maintained the am not sure if this is the same script that Vincent runs to create debs. I notice that it has gtk stuff hardcoded in, however from what I can see it appears that this script is only making one .deb rather than several.

Mattias, Vincent, is there anything I can do to assist you guys in cleaning up the deb packages?

One thing I can definitely offer is refinement of bash scripts. Ugly things, but I've learned that bastard of a language decently, for some reason.

Cheers,
David.

Clear instructions how to accompplish that would be welcome, kind of like the "how to setup a ubuntu repo" on the wiki.

Currently (snapshot) debs are build using make deb in a debian-sid chroot on a ubuntu 9.10 virtual machine. Previously it was done on plain ubuntu 9.10 virtual, but then there were some problems with dependencies of the gtk2 libs. They were set too high.

debian-sid has the advantage, that at least fpc is up to date. Do other debian versions have 2.4.0 already?

Vincent

I'll see what I can find. I am thinking that the best thing for me to do would be to see if I can replicate the build process you are performing right now, and then see what can be done differently.

Would it be possible for you to send me a copy of the scripts that you use for the deb building process? I could also set up a machine (real or virtual) with sid and work on this issue.

No, stable has 2.2.4. For this reason I access the sid repos for fpc only.

Cheers,
David.