This is the mail archive of the
mailing list for the Cygwin project.
Re: [RFC] splitting documentation
- From: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: cygwin-apps at cygwin dot com
- Date: Fri, 20 May 2016 17:10:00 +0200
- Subject: Re: [RFC] splitting documentation
- Authentication-results: sourceware.org; auth=none
- References: <d3964cef-fd56-3481-5e3d-c810f19ff998 at gmail dot com> <c655829d-d520-486f-66f7-a546ea819751 at dronecode dot org dot uk>
moving back to apps.
On 20/05/2016 16:41, Jon Turney wrote:
On 19/05/2016 22:34, Marco Atzeri wrote:
To move the documentation in a noarch package
I split lilypond in two source packages.
The documentation is just a copy of the upstream PDF so :
- the source package is a dummy to avoid data duplication
I can see why you want to do this, but I'm not sure it's a good idea.
One reason being, *IF* we were to ever end up in the situation where
only source packages were uploaded, and some build service constructed
the binary packages, that builder would not be permitted to download
I see no advantage for a build robot on this issue,
where we are just packing data.
As alternative there is no source package to be built
and we just put together the binary one.
$ cygcheck -l lilypond-doc
The packages with no source package are currently
R_autorebase Marco Atzeri
base-cygwin Corinna Vinschen
chere Dave Kilroy
cygcheck-dep Mikhail Usenko
plus all the
tesseract-ocr-<language> that are mine.