-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21/04/11 18:47, Rob Oakes wrote: > Hi Rainer,
Hi Rob > > My apologies for the delay in getting back to you. I've been meaning > to write for the better part of two weeks. And while I am generally > irresponsible, there are actually reasons for this delay ;) Two of > them, actually. Don't worry about the delay - I was just wondering if you went on a trip to the Amazon or if my mails got lost... ;) > > The first is a result of the general poor state of my scripts. I > wanted to make sure that they were working before I sent them to you. Absolutely understandable. > The short answer is that right now, they aren't. They never worked > very well. They were based on the debian scripts and a clean git > tarball. I, however, had all kinds of problems getting that to work > with Launchpad, so I used a variant of bzr deb. The resulting binary > packages were always way too big (~100 mb, rather than the ~20 they > should have been). That is definitely not right - 100mb is to much. But I remember also having debs created with checkinstall, which were about the same size... > > In the process of revising them, I came across this news story > describing Launchapd Recipes: > http://www.omgubuntu.co.uk/2011/04/launchpad-recipes-emerge-from-beta-wont-make-you-a-cake-but-packages-instead/ > > I haven't spent much time studying it yet, but I think it makes more > sense than the old system. For starters, we could create a bzr branch > of the stable 1.6 series, another for the stable 2.0 series, and a > third for LyX-Devel. Sounds reasonable. > It looks pretty easy to create regular releases > or even nightlies. That would be perfect - it would give a larger userbase to test new cutting edge non-stable versions of lyx. I assume that these can be packaged, that they can easily co-exist on one system? and update-alternatives could be used to link the lyx command to the newest stable version installed? > I'm interested in this since it would also let me > create packages from my LyX-Outline sources. The whole system is much > better than what I came up with. So it sounds like a win-win situation? > > To get this started, here's what we would need to do. > > 1.) Create a LyX SVN branch on Launchpad for 1.6, 2.0 and SVN. It can > be mirrored from our existing SVN and will pull in any changes > nightly. > 2.) Modify the existing package information that Ubuntu > already uses for building LyX. They are slightly different than the > ones that Debian uses. > 3.) Sit back and enjoy automated updates. > > Today, I'll get the import started for the SVN branches. If you're > still interested in helping, you could sign up for a Launchpad > account and apply for membership to the LyX-Outline-Devel team that > administers the existing PPA. > > https://launchpad.net/~lyx-outline-devel Done that. I hope that I will be able to help, Cheers, Rainer > > Cheers, > > Rob - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2wda4ACgkQoYgNqgF2egqdaACeNi+sWgpsi2hlLkePy9IXoag5 MfoAn0Wghg+9lCFSpbAJppzMWFCkvmKt =qiFz -----END PGP SIGNATURE-----
