On Sun, 29 Jun 2008 15:28:03 +0200, Matt Lawrence <[EMAIL PROTECTED]> wrote:
> The last email was a bit long. I'll try my best to make this short ;) > > You have an excellent package database system. This the core of any > installation method. However, what is needed is a flexible binary > package format. > Just to make things clear (I see you misuse it further down): we don't have a package database - or rather the filesystem is the database. The result from this is that you don't have to use a specific tool to insert/intergrate information into it, just cp, mv, and other file/ directory manipulation binaries. > When it comes to binaries, you can't get much more flexible than > binaries in an archive. This is the same principal you apply to > Compile, where you simply use the source code in an archive. Using > this principal, you download package information, download the > binaries from third-party website and add it to the system. This is > exactly what Zero Install does. > I don't know if this is what you stated above, but we do have a binary package format, binaries in an archive. We also support third-party, non-free binaries, like flash and video drivers by just unpacking them into our file system and symlinking them. Is this what you're after? > Sidenote: Is it be possible to use debs and RPMs with your > distribution and integrate it into your database? If so, this leaves > you unparalleled flexibility and incentive for people to install and > use your distribution. Just a thought. > It's easy to install a deb or rpm on GoboLinux; just do it as with other third-party, non-free binaries: unpack it into its own directory in the file system and symlink it. This will work for 99% of the cases because of the legacy symlinks, e.g /bin -> /System/Links/Executables > Does anyone think this is a good idea? If not, and I'm sure there are > probably good reasons why not, would someone please explain them to > me. > Problem with supporting installs from deb, rpm or any other package format is that we have to implement and support dependency tracking, and this with keeping a mapping database over what packages are compatible from the different package system. A database that would be hell to update and support, since the mapping isn't really 1:1. Something like deb2zero use (http://0install.net/deb2zero.html#id2714899), but more complex, since we already have two ways to install things on GoboLinux: from source and binary packages. I, myself, could think of having support for more package systems in GoboLinux, and I don't think there's a big opposition against it either. The real reason why it isn't done is: who will do it? None of the current developers see a personal need in having it. The request originates from users only. If someone implemented it and took responsibility for it it may see incorporation in our system (but I can't promise anything). GoboLinux is still too small to do these things and we have more interesting projects to spend our time on. By the way, user driven development has never been a good idea. :) -- /Jonas Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
