Bug#640737: [copyright-format] Format URL and installation on www.debian.org
On Sat, Oct 08, 2011 at 06:27:15PM +0900, Charles Plessy wrote:
> tag 640737 + patch
> thanks
>
> Dear all,
>
> to summarise:
>
> * http://www.debian.org/doc/packaging-manuals/copyright-format/<version>/ will
> allow the copyright-format specification to become a multi-page HTML document if
> it gets significantly expanded, but on the other hand, somebody downloading the
> current one-page spec will get a file called ‘index.html’.
>
> * Rebuilding the distributed document at each upload may cause it to change in
> layout or in checksum, but on the other hand ensures that it is continuously
> buildable.
>
> My point of view is that the copyright-format specification is not likely to be
> enlarged to the point of neeeding to separate its chapters in different files
> (there is SPDX…) and that the source document uses only simple DocBook 4.5 tags
> which makes it very unlikely to become unbuildable with the default XSL
> stylesheet it uses. Moreover, I am biased by the culture in my profession to
> not change even a single comma of a published work, so my personnal preference
> would have been to distribute files like copyright-format-1.0.html, committed
> with their source in the debian-policy Git repository. This said, this point of
> view had no support from other participants in this discussion.
>
> So I propose to do the following, in line with the other propositions.
>
> a) Apply the attached patch to point at http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ in the spec.
Fine with me.
> b) When the 1.0 version is finalised, (re)build at each upload copyright-format/copyright-format.xml,
> copyright-format/copyright-format-1.0.xml, and so on for the future revisions.
>
> c) Distribute the versionned and unversionned HTML and text builds in the
> debian-policy binary package. (Assuming that if since nobody proposed to stop
> distributing the unversionned build, it is that people want it to stay).
I am missing the disctinction between versionned and unversionned build.
What would be the purpose of the unversionned build ?
> I will propose a patch to implement the building and distribution of released
> versions and current draft, but before doing so, I would like to know if it
> would be acceptable to have them in /usr/share/doc/debian-policy, or if the
> published versions should be in a separate directory.
I think it is fine to put them in /usr/share/doc/debian-policy, or in a subdirectory,
as the need arise.
Cheers,
Bill.
Reply to: