I think that this PPA plan is pretty reasonable idea; if you're targeting just Ubuntu, then it will likely be less work than setting up your own apt repository (I'm happy to provide technical advice on either route).
I thought I'd clarify a few things about how PPAs work: (1) There is no technical review process for PPAs, so you don't need to worry about Debian policy items such as splitting out your giant monolithic package into individual packages; nobody is going to stop you. (2) There are lots of other packages, like the Linux kernel, that people build using Ubuntu PPAs that take several hours to build. So I don't think that building Sage there would be something the Launchpad admins would even notice. (3) They have a 1GB disk quota. This might be a showstopper problem, but I think it is possible to request a larger quota. I'd be happy to help with determining what parts of the (out of date) Sage package in Debian you'll need for this; I suspect that you will be able to save a substantial amount of time by starting from the debian/ directory from that. (Note that I'm not directly subscribed to this list and do not have the time to read it regularly, so you may want to CC me directly if you want to ensure I see your replies. I continue to wish that sage- devel was managed like the LKML.) -Tim Abbott On Oct 25, 1:45 am, Robert Bradshaw <rober...@math.washington.edu> wrote: > On Oct 24, 2009, at 6:08 PM, Dan Drake wrote: > > > > > On Sat, 24 Oct 2009 at 11:50AM -0700, William Stein wrote: > >> I don't know whatPPApackage means, but if we provide our own > >> repository, then certainly we can make a monolithic package as > >> described above. Moreover, there are genuine advantages, in that the > >> Debian package system will search through every single library in the > >> Sage install and make sure that the correct Debian packages are > >> listed > >> as dependencies. > > >PPAis "personal package archive": > >https://help.launchpad.net/Packaging/PPA > > > "Using a Personal Package Archive (PPA), you can distribute software > > and > > updates directly to Ubuntu users. Create your source package, upload > > it > > and Launchpad will build binaries and then host them in your own apt > > repository." > > > It looks like we'd need fully debianized packages for their build > > system, and would need to get everything to work with their > > buildbots -- > > and I suspect the Launchpad team would balk at having their buildbots > > work through Sage builds. On the other hand, making our own > > checkinstall-style packages and hosting our own repository shouldn't > > be > > too difficult. > > As well as easy of use (and I know downloading and extracting the > right binary from our site isn't hard, but it's not as easy as typing > apt-get), there's a certain perceived level of maturity that a project > gets by making it into a package management system. I've personally > been asked by people if they can "apt-get install sage" and am pretty > sure they would have if I could have told them yes. > > I don't know whether or not the launchpad team would balk at a > monolithic install that takes 3 hours to build, but it's certainly > worth a try. And if not, hosting it on our own looks really easy, and > once its set up building the .deb files shouldn't be any harder than > it is to build the current binaries. > > - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
