Open GoogleCodeExporter opened 9 years ago
Cool stuff. I don't know if anyone is planning to do this, but you should be
able to check out the svn repo, then do:
$ find . | grep "\.svn" | xargs rm -rf
To get rid of the Subversion directories and then tarball up the things you
want (mostly the editor/ folder, I suspect).
Original comment by codedr...@gmail.com
on 27 Aug 2010 at 4:13
Not what I meant, sorry.
I know how to checkout the repo :) -- the advantages of having a source tarball
distributed upstream are mainly:
1) no additional cruft in the packaging to get the original tarball. Normally,
we just "link" (not so simple, but it's like this) to the upstream website,
without a tarball I have to provide a Makefile target to re-generate it. It's
simple, but boring, at least (-:
2) other developers and users wanting to rebuild my package will be able to
compare hashsums between the tarball I upload in Debian, and the one hosted
here.
3) hashsum stability: as I said in point 1, providing a Makefile target to
create the tarball is easy -- the problem is that the hashsum isn't always the
same (tar's fault).
So it would be better if, in your release process, you also add a source
tarball. And if you could start providing one for what's currently released,
that would be über-great (-:
Thank you!
David
Original comment by d.pale...@gmail.com
on 27 Aug 2010 at 5:34
(and I'd need the whole trunk/, not only editor/ -- just without build/)
Original comment by d.pale...@gmail.com
on 27 Aug 2010 at 5:36
Attaching a patch against current SVN.
Original comment by d.pale...@gmail.com
on 27 Aug 2010 at 6:53
Attachments:
Applied in r1702 and r1703. Sadly my version of tar was unable to --exclude-vcs
and haven't manage to update it...so if you or maybe codedread would be so kind
to run the makefile and attach the resulting 2.5.1 tarball, that'd be great. :)
Original comment by adeve...@gmail.com
on 9 Sep 2010 at 4:39
Original issue reported on code.google.com by
d.pale...@gmail.com
on 24 Aug 2010 at 10:40