Apbuild 1.9.0 has been released. Major parts of the code has been cleaned up and some bugs have been fixed. The symbol list has been updated to the one used by the latest glibc. Apgcc now also supports the latest binutils's ld's '--as-needed' parameter. This allows apgcc to strip bogus dependencies much faster and much more reliably. It is recommended that you install the latest binutils. Apbuild now also includes a new tool called 'scandeps'. It scans your ELF binaries' library dependencies and generates a nice and easy-to-search report.
I've also uploaded a tarball with older GTK headers. Because GTK macros' values change between minor releases, they introduce dependencies on newer GTK symbols. Which means that your GTK 2.2 app may not work on GTK 2.2 systems anymore if you compile it with GTK 2.6 headers! Usage and installation instructions are included in the tarball.
Apbuild and the GTK headers can be found on the developer tools page.
The packager documentation page has been updated. The Writing Shared Libraries document has been added to the list of links.
Saturday 16th April 2005
We have delivered an Autopackage of the developer tools for packagers. You can find it on our developer tools page.
Sunday 10th April 2005
Version 1.0.1 has been released. This is a bugfix release. The announcement is here.
Wednesday 6th April 2005
There were some bad mistakes in the developer tarball. Some people were unable to install it. This has now been fixed, so if you couldn't install the developer tarball, try again.
Saturday 26th March 2005
Version 1.0 is here. The changes from 0.7 are bugfixes and the integration of the GUI managers which let you uninstall software easily (and in future, hopefully much more). We have also incorporated some great artwork from AJ Ashton, done using our very own Inkscape. Many new translations have been included, and more will appear over time in bugfix releases. Finally, packages that need newer versions of Autopackage will correctly upgrade the core code.
Most importantly, this is where we draw the line and promise not to break peoples packages with incompatible changes. From now on, it's a stable and mature piece of software.
Saturday 5th March 2005
There's now a Flash demo movie of the installation of the Gaim package.
Monday 7th February 2005The Packager Quick start guide has been revamped. It's doesn't look as boring anymore. :)
Friday 4th February 2005We revamped the FAQ to be easier to read and link to. It's also got some new content. It's generated directly from XML using a simple XSL transform.
Tuesday January 18th 2005A new translation status page has been created. It's right here.
Tuesday January 4th 2005The API documentation's look and design has been updated. Check it out.
Sunday January 2nd 2005Thanks to David Sansome, we have a sparkly new Packages Database, where you can add your package so others can find it. It's not meant to be a comprehensive database, rather just a nice way of tracking what packages are out there so you can see how people are using the technology. If you build a package, or know of one that isn't on the list, add it!
Thursday December 23rd 2004Autopackage 0.7 is here! New in this release:
- API stability: yes, we finally did it. The keystone is now in place, and you should feel free to start building auto packages. We will work hard to ensure they stay working, ideally forever. There are no plans to break backwards compatibility again in future.
- Initial support for sealed installers, i.e. self contained installers based on Autopackage that won't download things from the net and can resolve dependencies internally.
- The start of multiple CPU architecture support. Not complete yet, that can wait for after 1.0.
- Improved documentation
- Translation infrastructure for Autopackage itself is now in place. Translation will start immediately.
- Support for installing GConf schemas is now available
- A new graphical manager app for Qt/KDE users (GTK version available soon) that lets you easily uninstall packages.
Next stop: 1.0!
Thursday November 18th 2004Long time, no posts! Nope, we're not dead, however the maintainer has been in net exile for over three months. He has now returned and is once again hacking on the code. So what have we been working on in the meantime?
Well, firstly all the usual things: fixed many bugs, improved distro compatibility and so on. We've also started work on the developer education program, with the announcement of Writing Shared Libraries, a guide on how to write stable, versioned shared libraries. This is necessary as the instability of the underlying Linux platform is one of the biggest problems faced in trying to distribute distro-neutral binaries (indeed, distributing software at all).
We've also been hard at work designing a new GUI uninstaller/manager tool. In future we hope this will expand to support not just autopackages but the native distro packages as well. Screenshots will be uploaded soon!
Finally, whilst in exile I wrote up some notes on the Linux binary packaging scene, and a plan for how to reach the packaging utopia of up-to-date, high quality, on-demand distro neutral packages with a range of user interfaces.
Sunday July 18th 2004autopackage 0.6, named "Bragi", is out! New in this release:
- Distro compatibility fixes - bugs that showed up on SuSE and Slackware in particular
- Support for optional/recommended dependencies
- A new Quick Start guide for packagers
- Packaging of Autopackage itself has been improved, with better support for upgrades and a developer tarball
- Upgraded to a new luau which brings a better XML repository schema
- Supports root only installs now
- A new Qt based frontend, contributed by David Sansome
- Many bugfixes and lots of polishing. In the run up to 1.0, this is the bulk of the work.
No new features are planned until after 1.0 from this point onwards. The rest of the work is basically about bugfixing and adding a powerful API versioning scheme to autopackage itself.
You can test it easily by downloading the test packages from the downloads page.
Saturday June 12th 2004The first in what may become a series of weekly status updates is now available.
Sunday May 16th 2004Autopackage 0.5.1 has been released, which fixes an issue with the newest version of coreutils.
Sunday May 9th 2004We're pleased to announce the release of Autopackage 0.5, "deja vu". This release includes major improvements in almost every area:
- Improved documentation on binary portability
- Big improvements to the apbuild binary portability tool. It can now automatically remove unnecessary link options as a program is compiled. A new program to make soft linking easy has been added (relaytool).
- Package release numbers have been implemented
- Packages can now upgrade themselves in a simplistic style (by automatically removing the old version)
- We have native RPMs for the support code, for those who don't want Autopackage to install it automatically. These should work on pretty much any RPM based distribution.
- You can list the files of an installed package now
- You can once again run a .package direct from a graphical file manager, and it will all just work.
- A new graphical root password prompting program, autosu, is used to ask the user if they have the root password while still offering them the ability to install as non-root if they don't have it.
- New APIs for installing KDE mime files
- Lots of bugfixes!
In addition we've started working with other open source development teams to increase the range of test packages. As part of the 0.5 release, we've packaged Inkscape - grab the package from the downloads page. These are rolling nightly builds compiled straight from CVS, so be careful - they may not work perfectly. We've worked closely with the Inkscape guys to incorporate the necessary code and build system changes into their CVS repositories.
We're also working closely with the maintainer of Apollon, a KDE file sharing app to add the features they need to be able to distribute their software using Autopackage.
Wednesday April 21 2004
Today, a patch has been committed to the KDE CVS, which makes all KDE applications automatically relocatable on Linux (only apps though; libraries will still have to use BinReloc). Many thanks to Arend van Beelen Jr, who wrote the patch. He's the author of Apollon and offered to join us a while ago.
Wednesday April 7th 2004
The Guide to Making Relocatable Applications has been released. Linux apps are usually not relocatable (data paths are hardcoded at compile time). This guide explains what exactly the problem is and teaches you how to use BinReloc to make your application or library relocatable.
Tuesday April 6th 2004Some style sheets and images have been redesigned. Autopackage.org now has a new, smoother look.
Monday April 5th 2004We've had another change of plans: as of today we're heading full steam for 1.0 and will be skipping the previously planned 0.6 and 0.7 versions, which were supposed to be about adding RPM and native package repository (apt/emerge/urpmi) integration. There are quite a few people who want to use Autopackage now and not wait until we have every cool feature we could think of implemented. Because it's unlikely that these features will require a backwards compatibility break, we've decided to drop them until after 1.0.
After 0.5 is out, we will be heading straight into feature freeze, and working only on the things necessary to do a stable release. We've refocused on this goal because it's clear that two of the three primary developers no longer have enough time to make adding native package manager integration feasible this year, and we decided these features weren't critical to have. Hopefully with a stable release will come users, and with users will come developers.
Wednesday February 18th 2004Autopackage 0.4, codenamed "Better late than never ;)" is now available. New stuff includes but is not limited to:
- Easier, less error-prone package building process
- We now verify that binaries can be successfully linked as they are copied to the system
- Network dependency retrieval. This is the big one: two-phase downloads have been implemented, you can see a screen shot of the GTKFE showing this feature in the gallery.
- A whole ton of bugfixes, API improvements and so on
The next release will be focused on making more demo packages, improving documentation, and probably implementing package upgrades. We're hoping it will be a short time until 0.5 is out.
Tuesday Feburary 10th 2004After persistent hosting issues, we're in the middle of moving to sunsite.dk. These guys rock totally, I cannot recommend them enough. Hopefully we can soon get back to the codeface - 0.4 is nearly ready to ship!
Sunday January 11th 2004Another status update. We have network dependency resolution working fine, and are just shaking out the last remaining bugs (mostly binary portability and visual) remaining. We've also been busy moving everything across to a new server - this is on the same connection as before but should server should be a lot more stable. 0.4 is now in the release candidate stage - stay tuned for details!
Friday December 19th 2004Here's a quick status update, as it's been a while since the last release. We've been working hard on proper integration of network dependency retrieval, and are working with David Eklund of the luau project. I haven't had as much time as I'd like for the project recently - univeristy life combined with doing some freelance work on Wine have meant the project has moved slowly lately. Hopefully we can get a new release out over Christmas that has the network code integrated and working nicely.
Monday October 20th 2003
The 0.3.5 release of Autopackage is about polish, bugfixes, and small feature enhancements. New in this release:
- A new summary screen that shows you which packages and menu entries were installed
- Internationalization of specfiles - packages can now contain translated metadata.
- New DocBook based users guide
- Updated gaim packages along with packaged dependencies, such as GnuTLS.
- Better support for Red Hat distributions
- Cleaned up output
- Support for file(1) magic entries. autopackages themselves now have an entry.
- Lots of bugfixes!
You can get this release by downloading a package that needs it, for instance Gaim 0.70, and running it in the usual fashion. Have fun! :)
Wednesday October 1st 2003
PR stuff this time: in the last month we had a quick discussion at OSNews about the 0.3 release, and an interview at linmagau.org, check them out if you want more information on the project.
We're almost ready to release 0.3.5, which has a few new features but is primarily about polish and bugfixes. We've also massively improved the documentation - expect a nice packagers guide to appear on the website sometime in the next few days.
Wednesday September 3rd 2003
Today we release version 0.3 of the Autopackage software packaging and installation system. This release is not only more solid, more polished, and more featureful than the previous releases, but it contains many new modules as well.
Perhaps the most interesting new piece of code we wrote is the new GTK2 based graphical frontend. You can see some screen shots of it in the gallery. It's not yet 100% feature complete with the terminal frontend, for instance, it doesn't support interaction. While it's in no way finished, you can get an idea of what the final program will look like already.
We've also added code that will automatically download and setup the Autopackage support code and GTK frontend if it's not present on the system. This means that testing Autopackage is easier than ever before - all you need to do is choose a package, download, and run it. Just make sure you've uninstalled any previous versions of the software you may already have.
This release also sees the debut of two useful tools for building portable binaries: apbuild and binreloc. apbuild lets you compile your C or C++ application in such a way that it only uses old versions of the glibc symbols. binreloc lets you drop in some files and macros to make your application installable to any prefix, allowing you to install to users home directories, or distro-specific prefixes (like SuSEs /opt/kde3).
So what are you waiting for? Test it today!
Friday August 8th 2003This is just a quick status update, as due to our heavy use of IRC it's not always obvious where we're up to. As you can see if you look at the todo list, only a month on from the last release we already have many items completed, the most notable of which is the GTK GUI front end.
You can see some preliminary screen shots here:
- Intro screen
- Preparing the package
- Installing it
- ... and after it's finished
- it was already installed!
The final UI won't be exactly like this, in particular there's a whole load of polish we need to do to it.
I'll be away for a month starting on Monday, however work will continue on the code, and we'll probably be able to do a release once I get back in mid-late September time.
Saturday 12th July 2003The Autopackage project is pleased to announce the availability of version 0.2.6. The focus of this release has been robustness and a new dependencies system. New in this release:
- Automatically generated API documentation, available on the website (currently synced to CVS)
- Much better error handling. Rather than plough blindly on in the face of an error as the last release did, errors are now trapped, handled and will abort the install scripts.
- Better dependencies design. This is mostly documented in the "writing skeleton files" document, which you can find in the documentation section. As far as we know, this is the first attempt to cleanly split the concept of a packages interface version from the actual software version (which is the version the project assigns itself, for instance Widget2000). We hope that this scheme will prove flexible enough to deal with the mess that is the real world.
- A new visual ELF dependency walker. This is a Qt application which lets you see all the libraries an application needs in a tree - better than `ldd` as you can see the dependencies instead of a flat view, and easier than running objdump on each binary in turn. Very handy for locating the immediate dependencies of an app. Thanks to Filip for this.
- More fault tolerant tools. The `makeinstaller` program will now give you hints and warnings about your specfiles.
- More skeleton files for your packages.
Go grab it in the downloads section. Once again, please be aware that at this time any packages you build will be experimental only - package compatibility is frequently broken within several days. Packages you build with one release will not be compatible with future releases.
As a project, Autopackage seems to have settled into a fairly long release cycle. This one took approximately 2 months, previous releases have been similar. I'd like the release cycle to be shorter, but unfortunately doing a release takes quite a bit of effort, so I doubt that will happen soon. In particular, the next release won't be for some time - I am away travelling throughout most of August, and then will be starting university shortly after. Others on the project will hopefully continue to hack on the code, however a new release will probably not be coming out until mid to late September time.
As ever, if you want to know the latest status of the project, you can simply pop into #Autopackage on freenode and ask, or email the list. We'll be happy to update you on our progress.
Sunday 1st June 2003We are now connected to #commits on freenode, via CIA. Do the same for your project today!
Tuesday 27th May 2003... and now we have some documentation on the new skeleton system as well. Snarf it over at the developers section. Yell at me if some part of it doesn't make sense, or if you want more detail.
Saturday 24th May 2003We have API docs online! They are currently synced with CVS daily, same as the ChangeLog. Check it out in the developer section :)
Wednesday 7th May 2003Version 0.2.5 is done! Took long enough, that's for sure. Still, that's because a lot changed. Highlights of this release include:
- Local dependency resolution. This is the first step towards true apt-style functionality. It means packages will use any other .package files in the same directory to try and resolve dependencies.
- Internal reorganisation meaning that the package payloads are only decompressed when actually needed. That means packages start working faster, and that you're not using lots of disk space or memory keeping unneeded payloads hanging around. It'll also be useful for dialup users when we build the network in future.
- Integrity checking using MD5 hashes
- Setting the prefix must now be done from the command line. This is so most installs proceed automatically, as you should only rarely wish to alter the prefix, Autopackage will normally choose the best one for you. You can use the --prefix option if you need to do this
- Improved ramdisk code - packages will be decompressed to ram if you have enough leading to faster installs and improved performance in low disk space conditions
- Large improvements to the internal architecture, particularly with respect to the GUI protocol and skeletons system
- Some tools (not released yet) that allow you to compile portable binaries suitable for installation on a wide range of systems
A more detailed list of changes can be found in the white section of the TODO list, or the ChangeLog
These improvements, along with a larger collection of skeletons, means we've been able to package mplayer and the SDL libraries. If you want to try them, make sure you uninstall any previous copy of mplayer you may have, then download and run the package files after you performed the setup procedures. The mplayer as shipped by us is extremely basic - it has support for the GUI, a few codecs and not much else. You may find it useful though. If it doesn't work for some reason let us know.
The focus now will be on trying a new approach to dependency/package versioning, as well as improving the API docs and performing various misc fixes. We also want to tidy up the compilation tools and document it all. It hopefully won't take too long (touch wood).
Sunday 6th April 2003There hasn't been any news on this site for over a month, so I thought I'd give visitors a quick update. The code is progressing, check out the ChangeLog for details on what's been happening. A few of the highlights involve local dependency resolution (ie stick lots of .package files together in the same directory, run one and the dependency tree is walked). That's needed before we can do network based dependency resolution a la apt-get. Other interesting bits include a new documentation framework written by Curtis, and some new eye candy on the ttyfe.
The bulk of the work lately has been architectural, and I've also been busy with stuff for the packaging standards group. That's slowed down a bit lately, I think the time for discussion is drawing to a close for now and the time for spec writing has started. I'm still optimistic that we can achieve something useful there
The TODO list for 0.2.5 is nearly done. I think this will be the first release where we'll attempt to package something truly useful. Suggestions are welcome - I'm thinking mplayer? Not sure how much effort that'd require in terms of building out skeleton files though. Probably quite a bit.
Wednesday 5th March 2003There is an interview up on Newsforge, where we talk about the past, present and future of the project.
Tuesday 11th February 2003This is such a cool idea! I've seen this sport first hand, it's brilliant. I strongly suggest you try it, it's a convenient and portable form of amusement that can be used anywhere you don't mind embarrassing yourself or damaging other peoples property!.
Monday 10th February 2003We've started playing around with UI ideas for some Autopackage front ends, see them here. Work on the code progresses, but it's probably going to be a while until the next release.
Thursday 23rd January 2003Today we release 0.2.1, which was intended to be a simple bugfix and polish release, but along the way sprouted some new features from various contributors too :) Interesting changes include:
- Non-root installs: Thanks to Julien Olivier, it's now possible to install packages as root, in which case they'll be system wide and available to all users, or without root, in which it'll be installed only to your home directory. This mode will also deal with configuring the various paths and menu items as well, meaning you lose only a small amount of integration when doing things this way. Note that using root where possible is still recommended though
- Allow administrator overrides. If you don't want your users to be able to install .package files, you can now stop them
- Default choices for prefixes. For most people /usr/local will be fine, but if you like you can make each package install to its own directory now, for instance /apps/foobar
- We have a nice new progress bar now when decompressing the package from the console
- We scan LD_LIBRARY_PATH now when searching for libraries, meaning garnome style setups work fine
- compareVersions has seen many improvements thanks to Curtis Knight. We can now deal with a far wider range of version naming systems now, for instance 2.1-pre3 is known to be lower than 2.1
- And lots of bugfixes!
As usual, you can grab this download from here, follow the README carefully and if it doesn't work come and yell at us in IRC or on the mailing list
We're going to be improving some architectural stuff next. Hopefully 0.2.5 will come out fairly shortly, at which point it's open season for features again. In particular we want to have a prototype GTK2 gui by 0.3
Wednesday 18th December 2002There is a new code overview doc in the documentation section, and some new questions in the FAQ related to security.
Tuesday 10th December 2002For the past week we've had an article up at OSNews that talks about Linux packaging in general and how this project approaches the problem. If you've read the FAQ and still have questions, chances are that with 100 comments on the story, you can find an answer in there. Of course, if you still have questions, then ask me :)
Friday 6th December 2002Apologies to those of you who tried the gallery page only to find it was a 404, I forgot to commit CVS (again!!) Fixed now. Too bad there isn't much there yet, your creativity is somewhat limited by an xterm...
Thursday 5th December 2002Hurrah! Today we release autopackage 0.2, the culmination of several months of hard work. There have been a lot of changes, to get in depth details check out the ChangeLog. For those who prefer higher level overviews:
- An easier to use command line interface: package verify, package uninstall, package info and soon package install as well.
- Support for more file types. It can deal with shared libraries, desktop menu entries and man/info pages. It'll automatically register these things with the appropriate systems so for instance, even if you install to an unusual or package specific prefix the libraries will still be placed into the cache, entries will still appear in the menu (kde3 support for this is coming soon unfortunately but gnome2/gnome1.4/kde2 works ok), and manpages/infofiles will still be accessible. Note that if you don't want Autopackage to reconfigure the system for you this can be controlled by a preference.
- Global and user specific config files. In future versions the global config file can prevent the user specific config file from working, allowing administrators to prevent installation of .package files
- Simple metadata so the package can be queried without executing it
- Added code to properly allow you to install to any prefix you like and have things still work. Note: currently prefixes with spaces in don't work, that's on the TODO list to fix
- As ever, lots of bugfixes (the bulk of the work :)
The next version will be 0.2.1 and will concentrate on knocking off issues on the TODO list that are easily fixed. There are plenty of them, and so 0.2.1 will be a general polish/bugfix release. This is the best sort of time to get involved with development, because small patches are easily made and easily accepted. We need your help - the more developers we have, the faster Linux can get non-sucky software installation/package management and the faster we can move on to really making Linux a kick ass desktop for all. It's a long road to making all software truly easy to install, but that shouldn't discourage you from joining in. The best way is to join the mailing list and take offer to deal with an issue on the TODO list (take your pick). Another good idea is to join our channel on IRC - you don't even have to do any work, feel free to just watch what's going on and provide moral support ;)
Monday 2nd December 2002Hi there Slashdot. We got a some additions to our website a few days ago, amongst which was a web site stats counter. You can find it at the bottom of the page. The results are fascinating: virtually all our hits come from slashdot, there seems to be quite a bit of interest in the project. Some good news! 0.2 will be out very soon. Like, within the next few days. I've just written the README and all that's left is testing on a variety of distros.
Something else cool, check out the ChangeLog (link above). It updates daily from CVS, and as we do some work on it pretty much every day it's a good way to keep tabs on where we're up to
Finally, I've said it before, and I will most definitely say it again hundreds of times before we're done, but We Need You! So far there have been lots of website visitors and some people subscribe to the list, but only FoobarWidget has got off his backside and helped. Two of us is twice as good as just me, but we are still in need of more hackers, otherwise progress is going to be slow even with us working our backsides off. So if you have some spare time (i know, i know), but if you do then please stop by on IRC or the lists and help out. Hacking the code is dead easy, and we're happy to help bring you up to speed.
Thursday 21st November 2002More publicity, we have been listed over at VivaLinux, an Argentinian Linux website
Thursday 14th November 2002First things first, we got some free press over at PC Linux Online, so kudos to those guys for noticing our little project :) Publicity is something I've been trying to get, although we're not at the level where I want to start submitting stories to OSDN.
Secondly, some new questions have been added to the FAQ section, hopefully clearing up some of the woolier areas of the documentation. They address having a Qt/KDE gui, the projects relationship with GNU and a couple of other things
Thirdly, we have a code update for you. Progress is being made steadily for 0.2, although the 0.2 development series is dragging out far longer than I originally wanted. We keep finding things that simply have to go in before the next milestone :) I'm toying with the idea of doing a 0.1.9 release or something. A few of the recent changes:
- Switched to bzip2 for compression
- Stubs are tagged with metadata, so you can query package files (and later, packages from the database too)
- The various commands are being united into one "package" command, so you run "package query foobar.package" or "package install gimp" for instance. This simplifies the code and the CLI ui somewhat.
- We have system and user config files now. These are actually just bash scripts that are sourced into Autopackage as needed, so you've got quite a bit of flexibility in switching config options on and off etc. This change was prompted by the addition of the library install routines.
- Support for more file types. Hongli put together a foobar package which contains files of lots of different types (ie binaries, man pages, info docs, .desktop files, icons, shared libs, data files etc) so we could test our support for them. autopackages can now easily update desktop menus for GNOME and KDE. Hopefully as vFolders mature the need for this will lessen somewhat, but for now it's a nice feature to have.
- When installing libraries, Autopackage can update the linker cache configuration (ld.so.conf) for you. As this feature got mixed responses in IRC, with the more hardcore types disliking it and newer users thinking it was a good idea, it's a preference that can be set when Autopackage is first set up. If the cache isn't updated, you'll get a warning.
- Starting on support for usermode installs, so it's possible to install software without being root. This is mainly architectural work right now, you still need to be root to install .package files at present. This will hopefully change sometime after 0.2 or 0.3
We've gone too long without news on this page. Me and Hongli have been bashing our way
through the bugs and improvements. We haven't reached 0.2 yet, but lots of good changes have
been made that weren't on the schedule, but probably should have been. Here's a quick selection:
- Biggest addition is probably libprefixdb, which allows us to deprefix apps. There's more info about this in the documentation section. This allows you to choose any prefix you want for an app
- Autopackage itself is deprefixed now to some extent, though at the moment you get exactly 1 choice: /usr/local - you will get a choice later
- Lots of bugfixes and improvements, it's much easier to setup and remove now thanks to dedicated scripts.
- Better source code organization and documentation
- Bug fixes related to building multiple packages at once
- Improved (un)preparation mechanism.
Hopefully we'll be able to add features more easily for 0.2 from now on, which will feature support for more file types (we have a testbed app to play with now too). What's also nice is that we've had 11,000 hits since launch :) Good to know people are interested.
And finally, we have an announcements list so if you're interested in following the project, you can sign up to that instead of the dev list.
Wednesday 25th September 2002A few updates, thanks to Hongli a bug was fixed in the genst module that led autotools to refer to an out of date specfile name. There is also a new article in the documentation section that explains how the Autopackage database system works, and how to use it. Finally, there is now a tarball of genst a simple utility that you can test out Autopackage on in the downloads section. I should have thought of that before, but there you go.
Sunday 22nd September 2002Huh? For some reason the new freshmeat page says this software is "Free to use but restricted". I'd like to point out that this software is actually under the GPL, it most certainly not is restricted, so if you were wondering about that, either me or the freshmeat team messed up.
Sunday 22nd September 2002Well, it's up :) I've also set up the mailman software and the CVS repository. Hopefully soon bugzilla will be up too, but for now this is good enough. Also added docs on the problem of non-relocatability (prefixification), but haven't yet fully written the code to help solve this problem. We also now have exceptions in bash! (well, sort of). Take a look at the failsafing document for more info.
Wednesday 24th July 2002Started work on the Autopackage website. Hopefully it'll soon be up on the web :)