[Pkg-fonts-devel] converting fontforge packaging repo to git
kamathvasudev at gmail.com
Fri Feb 3 04:47:50 UTC 2012
On Fri, Feb 3, 2012 at 6:50 AM, Daniel Kahn Gillmor
<dkg at fifthhorseman.net> wrote:
> Hum, this looks like it's just two commits: one containing the upstream
> tarball, and one containing the current changeset. This includes
> nothing of the history i was hoping to get, and it doesn't even seem to
> build off of upstream's history either.
Yep I just imported existing version of fontforge package from Debian
into this repo.
> I'd like to see something that integrates and stores the history that we
> do have available.
Getting packaging histroy from svn is not very easy but as long as svn
repo lies arround this history will also be present there that was my
thought and that is how we implemented Git repo in Debian-IN and also
We may be able to mirror repo on upstream release by using git build
package. I'm really not sure how we can do that but I'll try digging
into it :)
> Sorry i haven't been able to work on this yet. I'm trying to get my
> head around the right way to do it, and i might just punt shortly and
> throw up a link to a half-assed version that at least contains all the
> revision history.
> The bad news, as i trawl the various repos and compare them to the
> actual released tarballs, is that fontforge release practice has been
> sloppy at best. of the tarballs that we've built from, very few of them
> are a clean/direct mapping from the upstream revision control system.
> there's almost always a bunch of (unnecessary, imho) fiddling that goes
> on between upstream's vcs and their release.
> The good news is that i think i see a way to short-circuit that, and
> provide clean debian releases from the upstream VCS.
> So if you can hang tight for another day or so, i hope to have something
> to present that folks can pick apart.
Sure I'll hang arround :)
> apologies for the delay!
No problem :)
More information about the Pkg-fonts-devel