Re: dgit and upstream git repos
On 9 October 2014 15:38, Ian Jackson <ijackson@chiark.greenend.org.uk> wrote:
> Dimitri John Ledkov writes ("Re: dgit and upstream git repos"):
>> Sounds intriguing, can you please share design / intentions there?
>
> I haven't done the research needed yet. Facts are welcome.
>
> In particular...
>
>> git-dpm currently generates debian/patches/* with patches against the
>> tree applied but without generating/storing .pc directory.
>> And surprisingly dpkg-source works fine with that. Thus maybe the dgit
>> sanity check can be adjusted to insure there is no diff between
>> unpacked source package & git tree, sans .pc ? Because at the moment
>> for example: quilt push -a, generates .timestamp files (which
>> dpkg-source does not), hence `git add .pc; git commit -a -m "quilt
>> spew"; dgit build -S` bombs out asking one to delete .timestamp files
>> from the git tree.
>
> ... I had thought that the stuff in .pc is necessary for dpkg-source
> to be able to build the package, and unpack the result.
>
> If I can feed a .pc-less source tree to dpkg-source -b and get
> roughtly the right output then that would obviously be a big
> improvement.
$ apt-get source sword
$ cd sword-*
$ rm -rf .pc
# a tree with up-to-date debian/patches, all patches are applied (as
e.g. git-dpm does), .pc directory is gone
$ dpkg-source -b .
$ echo $?
0
--
Regards,
Dimitri.
Reply to: