--- Matthew Johnson <firstname.lastname@example.org> escribió:
> On Thu, 1 Feb 2007, Miriam Ruiz wrote:
> > I've temporarily placed my current debian/ directory for Frets on Fire at:
> > http://users.alioth.debian.org/~baby-guest/fretsonfire/debian.tgz
> New one here: http://mjj29.matthew.ath.cx/fretsonfire-debian.tar.gz
Great!! I'm having a look at it right now :)
> I've updated a bunch of stuff in the debian directory (see the
> changelog) and done some general tidying. The only lintian errors left
> are that a bunch of data files are install executable, these should be
> changed either when creating the orig.tar.gz, or in the install target
> by using install -m rather than cp.
> > I'm sorry I cannot add it to SVN yet due to some firewall here :(
> Do you want me to do that?
Yes, please! :)
Please, put me as uploader instead of maintainer, and set the maintainer field
Maintainer: Debian Games Team <email@example.com>
> > To get the orig.tar.gz file, which must be re-created because the code
> must be
> > fetched from a different .tgz than the data, see the get-orig-function in
> > debian/rules. The orig is nearly 30 Mb so I won't upload mine.
> also, upstream's website is currently broken, and some of the links now
> go via sourceforge's mirror pages.
Aha, I hadn't noticed that. Cool :)
> > 5) Once we know which data we'll include, separate package in two:
> > fretsonfire/any and fretsonfire-data/all
> Are we going to compile the python files then? it currently works fine
> without doing so on mine (as a -all package).
I think python-supports adds the needed commands to
preinst/postinst/prerm/postrm scripts to compile the .py files to .pyc on
install, so I don't need we should worry about that. I wouldn't pack it in a
bunch for Debian as upstream does, I don't think there's any need for that. We
should just follow Debian's Python policy .
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.