[gccsdk] riscos.info package repository

As anyone who's been watching the SVN commits might have noticed, I've been
doing a bit of work in fixing up a lot of the packaged software on
riscos.info that's broken (not ARMv7 compatible etc). So quite a few
packages now have updates.

In addition to this, because I can't contact Graham, I've merged in the
package index from riscpkg.org to create a unified list of packages. Along
the way various things get blacklisted - for example, things on riscpkg.org
relating to GCC 2.95 - either because they won't work on ARMv7, or they're
just plain confusing. The packages themselves are still there, but not
indexed.

For your RiscPkg/PackMan sources file, the new index is here:
http://www.riscos.info/packages/pkg/raspberrypi

The plan is to ship ROOL's RaspberryPi SD card image with PackMan ready
configured and pointing at this index, so users can install this packaged
software. As much as is possible on the SD image is managed, so updates can
be easily pushed out, and there's a RaspberryPiDistro dummy package to use
to lever future upgrades of other parts of the system.

There are already some binary-only packages I've put into the autobuilder
tree, which the autobuilder makes by downloading zip files of binaries from
the author's website and moving files around. This means anyone running the
autobuilder can rebuild those packages (the idea is they'll be trivial to
update when upgrades are released).

Now I'm starting to get people send me packages to include. At the moment,
I haven't written any infrastructure to cope with this so I'm just
importing them manually.

So, a question: should third-party packages (those which aren't autobuilt)
be included in the riscos.info package repository? At the moment I've set
them up as a separate repository in my riscos.info home directory and then
my merge script joins the indexes together. That means they're hidden from
the normal autobuilder web pages.

In terms of infrastructure for auto updates I haven't really decided, but am
thinking of something simple like a script that always fetches zips from a
fixed URL (ie http://upstream/mypkg.zip not mypkg1.2.3.zip), run from a cron
job or magic cgi location to force an index rebuild. Then maybe also a URL
watcher to email for watching those upstream pages where some autobuilder
poking is required. Am open to ideas.

Thoughts?
Theo

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK