STklos
STklos copied to clipboard
egallesio
Debian package
We started a group to try and package more Scheme implementations for Debian. Would you like to have a Debian package for STklos, and do you consider the latest release 1.50 ready for packaging?
@egallesio can speak ref. stability etc. Anyway, I think it would be great to have a Debain package! It would bring many more users!
group to try and package more Scheme implementations for Debian
@lassik which group is that? (I am a Debian user since... Uh, not sure -- since the dawn of time!)
which group is that?
https://salsa.debian.org/scheme-team https://lists.debian.org/debian-scheme/
Do you want to join?
Do you want to join?
Yes - but I'm not a Debian developer (not even maintainer)
Me neither. It's possible for non-DDs to join the above mailing list and GitLab instance as well.
We started a group to try and package more Scheme implementations for Debian. Would you like to have a Debian package for STklos, and do you consider the latest release 1.50 ready for packaging?
Wow, it's a great news!. Having a Debian package for STklos would be really a good thing for the project.
1.50 should be OK for a package I think.
For next releases, is it easier for the team if the debian package is included in the upstream version or, on contrary, easier to maintain if it's kept separately? In any case, tell me what I need to do to ease the work of maintainers.
I have subscribed the mailing list and I'll have a look at the Gitlab repository (I will not have time to be active on it for now, but will do my best to help, if needed).
Thanks for giving us the green light :)
Some remarks from @weinholt who is an experienced Scheme and Debian developer (@jpellegrini and I have never packaged anything for Debian so he is mentoring us):
I added a workaround in debian/rules for some files that aren't removed by make clean. Those should be fixed in the upstream repository.
I haven't looked at the other problems yet, you're both welcome to have a look.
Another problem is that stklos-config embeds CFLAGS from the package build, which contains the build directory...
Jeronimo: Is the bytecode format portable between architectures and operating systems? I think we should move the /usr/share/stklos/1.50/* files to a stklos-common package to save space in the Debian archive. But can e.g. an ARM computer use the *.ostk files built on AMD64?
There are also some questions around how to package the C development part of STklos. It should probably be separate from the main stklos package, but I didn't see any libraries and don't know how it works.
And lintian complains that srfi-175-impl.so shouldn't be in /usr/share.
Here's the STklos Debian packaging repo: https://salsa.debian.org/scheme-team/stklos
Here's the STklos Debian packaging repo: https://salsa.debian.org/scheme-team/stklos
I didn't see a way to pos issues in this repo (I'm not registered yet), to answer some of the questions above and for some comment (for instance stklos-compile and stklos-genlex should not be deleted form the install).
I'll have a look later this week.
stklos-compile and stklos-genlex should not be deleted form the install
I think they meant "deleted by make clean", no?
But anyway, as far as I see, make clean already does that.
Here's the STklos Debian packaging repo: https://salsa.debian.org/scheme-team/stklos
I didn't see a way to pos issues in this repo (I'm not registered yet)
Registration is needed to comment. But you don't need to be a Debian Developer or Debian Maintainer to register - anyone can make an account from the web UI. If you do, please email @weinholt your username; he has admin access to the Scheme team and can give you the necessary rights.