public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: [RFC] splitting documentation
Date: Thu, 19 May 2016 21:35:00 -0000	[thread overview]
Message-ID: <d3964cef-fd56-3481-5e3d-c810f19ff998@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

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
- the install phase phase grab the files from upstream an put in
the proper directory.

Question:
- How to properly replace the old layout with the
  new in upload ?

I expect that "calm" could complain about:

x86/release/lilypond/lilypond-doc/lilypond-doc-2.19.37-1.tar.xz
noarch/release/lilypond-doc/lilypond-doc-2.19.42-1.tar.xz

Should I move both as :

noarch/release/lilypond-doc/lilypond-doc-2.19.37-1.tar.xz
noarch/release/lilypond-doc/lilypond-doc-2.19.42-1.tar.xz

Regards
Marco





[-- Attachment #2: lilypond-doc.cygport --]
[-- Type: text/plain, Size: 1309 bytes --]

# lilypond.cygport
NAME="lilypond-doc"
VERSION=2.19.42
RELEASE=1
ARCH="noarch"
SUMMARY="A typesetting system for music notation (Documentation)"
DESCRIPTION="LilyPond is an automated music engraving system. It formats music beautifully and automatically, and has a friendly syntax for its input files."
CATEGORY="Interpreters"

MAJOR_VERSION="$(echo ${VERSION} | cut -d '.' -f 1)"
MINOR_VERSION="$(echo ${VERSION} | cut -d '.' -f 2)"

# PATCH_URI=""

HOMEPAGE="http://www.lilypond.org/"
SRC_URI="empty.tar.xz"
SRC_DIR="empty"

PKG_NAMES="lilypond-doc"
RESTRICT="diff"

# The main 'lilypond' package contains everything except the PDF 
# documentation.

# The 'lilypond-doc' package.
lilypond_doc_CONTENTS="usr/share/doc/lilypond/pdf"
lilypond_doc_SUMMARY="Documentation for LilyPond."
lilypond_doc_DESCRIPTION="${DESCRIPTION} This package contains the documentation for LilyPond."
lilypond_doc_CATEGORY="Doc"

src_compile() {
	:
}


src_install() {
        dodir  /usr/share/doc/lilypond/pdf
	cd ${D}/usr/share/doc/lilypond/pdf
	wget http://lilypond.org/doc/v2.19/Documentation/learning.pdf
	wget http://lilypond.org/doc/v2.19/Documentation/music-glossary.pdf
	wget http://lilypond.org/doc/v2.19/Documentation/essay.pdf
	wget http://lilypond.org/doc/v2.19/Documentation/usage.pdf
}

src_test() {
        :
}


             reply	other threads:[~2016-05-19 21:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 21:35 Marco Atzeri [this message]
     [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

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=d3964cef-fd56-3481-5e3d-c810f19ff998@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).