[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PATCH] proposed v3 source format using .git.tar.gz

On Tue, 9 Oct 2007 14:17:17 +1000, Anthony Towns <aj@azure.humbug.org.au> said: 

> So that leaves:

>> I still think that shipping a full working dir, with no dpkg changes,
>> seem to be the way to go, along with a tla grab file, which I think I
>> should consider putting into the package itself (If I can work around
>> the chicken and egg issue of adding a grab file changes the source
>> revision which means the grab file should change which means a new
>> revision is needed ....)

> If you're just distributing a snapshot, rather than a full repository
> as Joey's basically proposing, why can't your grab file be
> autogenerated? ie,

> 	1. hack on the source, merge changes, blahblah, finish, tag
> 	2. do a checkout from version control
> 	3. autogenerate anything necessary
> 	4. create source package
> 	5. build
> 	6. upload

> If you're using pristine-tar to create a pristine .orig.tgz from your
> repo (rather than keeping one around), that needs to be autogenerated
> at step 3 too, afaics. Worst case you could check the autogenerated
> files into a parallel repository and use a config or something,
> afaics.

        I can (and do) autogenerate the grab file -- and I guess I can
 add it to the source package after I check things out of the version
 control. I guess I was quibbling over having stuff in the source
 package that was not  in my version control and not generated by dpkg
 and friends -- but even I can see it is a pretty weak quibble.

        Anyway, thanks for the clarifications: I'll just re-start
 shipping a full working sir in the source tree, along with a grab file
 for registration; the overhead is pretty minimal compared to that of
 the full repo that git ships; and if people can deal with .git dirs,
 they can deal with {arch} and .arch-id dirs  as well.

        Which concludes my involvement in this thread.

"He flung himself on his horse and rode madly off in all directions."
Manoj Srivastava <srivasta@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: