[Debian-olpc-devel] Packaging without an upstream tarball

[Luke Faraone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/05/2010 07:14 AM, David Farning wrote:
> Luke,your getting started guide used a tarball as a starting point...
> but several of the activities don't have an up to date tarball on
> download.sl.o.
> 
> It is possible to start packaging an activity by pointing to a
> existing repository on git.sl.o rather than doing a pristine import.

I think it's possible to do this using upstream git on a branch and
using tagging, but I'm not too clear on how to do that. Jonas, would you
happen to know more about this?

What I would advise is to create a upstream tarball using a
get-orig-source rule like what I have attached.

This rule attempts to checkout the upstream git source, looks for a git
tag if present with the current version, and alternatively supports git
snapshots. (version numbers like "87+git228cd65")

- -- 
Luke Faraone
http://luke.faraone.cc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkwyEUQACgkQtrC51grHAgbL7wCfTtrg6wVUYJFd4AJ2n8riuPZe
yEMAn2TEdkSPhylOHDnPuitLSjSjwGc3
=c4dM
-----END PGP SIGNATURE-----
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: git-get-orig-source
URL: <http://lists.alioth.debian.org/pipermail/debian-olpc-devel/attachments/20100705/115c70ce/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: git-get-orig-source.sig
Type: application/octet-stream
Size: 72 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-olpc-devel/attachments/20100705/115c70ce/attachment.obj>