On Mon, 2008-09-15 at 16:26 +0300, Igor Stasenko wrote:
2008/9/15 Norbert Hartl <norbert@hartl.name>:
On Mon, 2008-09-15 at 14:44 +0300, Igor Stasenko wrote:
2008/9/15 Norbert Hartl <norbert@hartl.name>:
On Mon, 2008-09-15 at 09:53 +0300, Igor Stasenko wrote:
2008/9/15 Norbert Hartl <norbert@hartl.name>:
On Mon, 2008-09-15 at 03:36 +0300, Igor Stasenko wrote:
I managed to build squeak + freetype plugin on my ubuntu box. Not sure, however how to package resulting binary.
I took a look at the svn repo and there is indeed no other option than installing the binary in the system. I wonder how the vm is usually packed. The links on squeakvm.org for the redhat and debian packages are disabled, too.
I can help building debian packages. Maybe it would be good the check in the debian files into svn for easy package creation.
yes, something like 'make bin-package' would be cool
Btw, Ubuntu having a squeak in its binary packages collection, so i think its better to contact with people who actually did it instead of repeating doing same. But i can't remember who actually made it.
Ah btw. do you know apt-src??? Try to do
apt-src install squeak-vm
well, it deals with source packages, not binary. People who care to build squeak from sources should really get it from squeakvm.org not from other sources. IMO.
I'm sure the sources are taken from squeakvm.org. It's just that a system like debian has source snapshots. So to build a certain version of a package you export those sources into the debian skeleton and build the binary from there. This way maintainer and others are able to build the same package from the same sources. If sources are updated you need to create a new version. It just differs in the way you do it. Using a tag from svn to get sources is not the way debian handles it.
Yeah, but how would you deal with sources generated by VMMaker? We having two sources participating in final result: - VMMaker - platforms source.
unlike from C world, where everything in single package.
Should such distribution include a VMMaker sources, and then , in some way build everything from scratch (which requires to having some version of squeak installed already)? Otherwise you need to carry the snapshot of generated sources in this package, which i really don't like.
I don't think there are much alternatives. Somehow you have to freeze the state of the sources. No need to recreate a fixed state with a tool like VMMaker. After VMMaker has finished it is just a bunch of C files. Creating a copy/snapshot of it isn't that bad even if includes svn and vmmaker sources. The rationale behind the deb-src is that there is e.g. a security team in debian that can patch the whole thing if they find a security problem in the sources. That means a debian package is the binary compiled from sources (snapshot) plus patches from the one maintaining the package plus patches from the debian team plus patches from the security team... :) The average user isn't using deb-src. The open source just enables you to do so if you have the need to. Including a plugin in the vm is good use case for that. You take the deb-src and adjust it to your need. If you find the sources being outdated you can email the maintainer. If you want to include stuff do the same. If it is all to tedious or slow you might try _being_ the maintainer ;) Norbert
That's why i'm thinking that best would to distribute binary, not sources. And people who like to build everything from scratch should be pointed to squeakvm.org (or any other site, where such binary came from).
We're getting back to discussion on squeak-dev, that debian people don't want to include squeak in their main repository (or how do they call it). Because squeak don't have a process which can recreate image purely from source files, and because it is complete stupidity :)
Please have a look at the debian/changelog file. That is the file where the builder takes the version number from. A comment what has changed comes along with it.
The easiest way to deal with this is to integrate the debian skeleton in the squeakvm repository. Than you can checkout svn and create a package from it. And someone needs to update the debian repository so the new vm is integrated in the next release.
Norbert