From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] splitting documentation
Date: Fri, 20 May 2016 19:47:00 -0000 [thread overview]
Message-ID: <0f3ae3fe-604a-53ec-e344-3eb2d96f53d7@gmail.com> (raw)
In-Reply-To: <87k2io7fqu.fsf@Rainer.invalid>
On 20/05/2016 20:20, Achim Gratz wrote:
> Marco Atzeri writes:
>> To move the documentation in a noarch package
>> I split lilypond in two source packages.
>
> I'm not too enamored with this idea… we will eventually end up with the
> possibility of having parts of packages noarch and other parts arch-ful.
> Trying to preempt that goal by going berserk on package definitions that
> are not noarch only seems wrong to me.
>
>
> Regards,
> Achim.
In this case is not documentation built from the source,
it is separately downloaded already now, just packaged
together for convenience.
Putting in noarch reduce the duplication.
SRC_URI="http://download.linuxaudio.org/${PN}/sources/v${MAJOR_VERSION}.${MINOR_VERSION}/${P}.tar.gz
http://www.lilypond.org/doc/v2.19/Documentation/learning.pdf"
src_install() {
...
insinto /usr/share/doc/lilypond/pdf
doins ${S}/learning.pdf
}
currently there are 4 copies of learning.pdf
(source + binary) for each arch.
Marco
prev parent reply other threads:[~2016-05-20 19:47 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
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 [this message]
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=0f3ae3fe-604a-53ec-e344-3eb2d96f53d7@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).