Import layout of Quilt v3 packages

[Martin Pool]

On 8 February 2011 19:00, Max Bowsher <maxb at f2s.com> wrote:
> On 08/02/11 07:00, Martin Pool wrote:
>> At the moment it seems to me we need to either: import to looms and
>> mandate using looms; or check in things with everything expanded and
>> provide glue that will keep the quilt data up to date with the wt.
>> (Perhaps they should be considered derived data and updated from a
>> hook.)
>
> I don't think we want to be checking in .pc at all.
>
> Personally I quite like the simplicity of just checking in the package
> with the patches NOT applied, but I gather people like being able to
> navigate the actual history of the patched package.
>
> Therefore, what about checking in the patched code, without any quilt
> metadata (.pc dir) but with a flag file that triggers bzr-builddeb to
> write out the appropriate metadata whenever a working tree is built for
> such a branch?
>
> (Writing out the metadata would consist of copying the series file to
> .pc/applied-patches, and reverse-applying each patch in reverse order,
> stashing the resultant modified file in .pc/<patchname>/<filename> for
> each patch)

Right, that's what I meant by my (somewhat unclear) second option.