From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] splitting documentation
Date: Fri, 20 May 2016 15:10:00 -0000 [thread overview]
Message-ID: <bf4f9942-05de-7c72-9de9-4d9cbdc4d1e3@gmail.com> (raw)
In-Reply-To: <c655829d-d520-486f-66f7-a546ea819751@dronecode.org.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.
>>
>> http://matzeri.altervista.org/noarch/lilypond-doc/
>> http://matzeri.altervista.org/x86/lilypond/
>> http://matzeri.altervista.org/x86_64/lilypond/
>>
>> 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
> arbitrary files.
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
/usr/share/doc/lilypond/pdf/essay.pdf
/usr/share/doc/lilypond/pdf/learning.pdf
/usr/share/doc/lilypond/pdf/music-glossary.pdf
/usr/share/doc/lilypond/pdf/usage.pdf
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.
Regards
Marco
next prev parent reply other threads:[~2016-05-20 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 21:35 Marco Atzeri
[not found] ` <c655829d-d520-486f-66f7-a546ea819751@dronecode.org.uk>
2016-05-20 15:10 ` Marco Atzeri [this message]
2016-05-23 14:00 ` Jon Turney
2016-05-23 14:16 ` Marco Atzeri
2016-05-20 18:21 ` Achim Gratz
2016-05-20 19:47 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf4f9942-05de-7c72-9de9-4d9cbdc4d1e3@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).