Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-09-01 Thread Russ Allbery
Bill Allombert writes: > On Fri, Aug 27, 2010 at 03:50:02PM -0700, Russ Allbery wrote: >> Bill, do you mind if we make Emacs a build requirement for Policy for >> the *.org files that are in there right now? I think you were the one >> who expressed concerns previously about the org files. > em

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-31 Thread Ben Finney
Bill Allombert writes: > On Fri, Aug 27, 2010 at 03:50:02PM -0700, Russ Allbery wrote: > > Bill, do you mind if we make Emacs a build requirement for Policy > > for the *.org files that are in there right now? I think you were > > the one who expressed concerns previously about the org files. > >

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-31 Thread Bill Allombert
On Fri, Aug 27, 2010 at 03:50:02PM -0700, Russ Allbery wrote: > Ben Finney writes: > > Russ Allbery writes: > > >> If that's no longer a concern, I can remove the generated files and > >> build them from debian/rules by default. > > > (And add ‘emacs’ to ‘Build-Depends-Indep’, I assume.) > > >

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-27 Thread Russ Allbery
Ben Finney writes: > Russ Allbery writes: >> If that's no longer a concern, I can remove the generated files and >> build them from debian/rules by default. > (And add ‘emacs’ to ‘Build-Depends-Indep’, I assume.) > I don't know for whom it was a concern. How will we know if those > concerns ar

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-27 Thread Ben Finney
Russ Allbery writes: > This was intentional when those files were introduced since rebuilding > them requires Emacs, and the concern was that not everyone who worked > on Policy would want to have Emacs installed. Thanks for the explanation. I think that Emacs should simply be a build dependenc

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-27 Thread Russ Allbery
Ben Finney writes: > The VCS repository for ‘debian-policy’ contains a source document > ‘README.org’ along with rules to render that to the destination > documents. > However, the VCS repository also contains the rendered documents > themselves. Those should not be tracked in VCS; instead, they

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-24 Thread Ben Finney
Andrew McMillan writes: > On Wed, 2010-08-25 at 14:28 +1000, Ben Finney wrote: > > I couldn't find a way to tell Git “these files are removed from the > > repository, propagate that fact to other repositories”. (Git doesn't > > seem to track file removal as such, making me wonder if it's even > >

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-24 Thread Andrew McMillan
On Wed, 2010-08-25 at 14:28 +1000, Ben Finney wrote: > On 25-Aug-2010, Ben Finney wrote: > > However, the VCS repository also contains the rendered documents > > themselves. Those should not be tracked in VCS; instead, they should > > be generated from source as needed. > > I couldn't find a way t

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-24 Thread Ben Finney
On 25-Aug-2010, Ben Finney wrote: > However, the VCS repository also contains the rendered documents > themselves. Those should not be tracked in VCS; instead, they should > be generated from source as needed. I couldn't find a way to tell Git “these files are removed from the repository, propagat

Bug#594274: debian-policy: Don't track generated README documents in VCS

2010-08-24 Thread Ben Finney
Package: debian-policy Version: 3.9.1.0 Severity: minor The VCS repository for ‘debian-policy’ contains a source document ‘README.org’ along with rules to render that to the destination documents. However, the VCS repository also contains the rendered documents themselves. Those should not be tra