X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=hno0QgRuzXZ1rlkv 2UIfP4anC4lcSnhLAdFSQXfCAxZhw1G8tnwwl/DNGAitghCSNi2axTNvESVaGl8+ 6cXQI6RhUipyJl/qbVZIS+f4tgsklqYhAkA8sv8wzSLQekCciHrtxw9Hxi7ifIWL WXhbx3DDAXQsoNsnvnbWxI38KTM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=no/GtLUX4mfGsN+Sbs8ZhV E3B3Y=; b=fedJkZMNRExGMN604vTtibjJ1dTy0prAW7unJEkm6ld/c63bxKIutk q3oVtPesnqEz7RP88HyExJyq1iP/8AK9DpJoqS03MLgJREyBHODPItJoreUsWhL5 EnvVB+uij3JL8+fBStqXpRI/6LnfmmOlOYj6jM1pgo/m4tAZqp20w= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=PDF, Hx-spam-relays-external:ESMTPA X-HELO: out3-smtp.messagingengine.com Subject: Re: [RFC] splitting documentation To: cygwin AT cygwin DOT com References: From: Jon Turney Message-ID: Date: Fri, 20 May 2016 15:41:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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. > - 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 Yes, this is not permitted (at the moment). All versions of a package in the package set for a given arch must lie on the same path. (This limitation is tangled up with how we determine if a package upload is permitted, so isn't straightforward to remove) > 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 Move the existing 2.19.37-1 x86/x86_64 package to noarch, then upload of 2.19.42-1 will be permitted (using cygport 0.22.0 or later, which knows to upload noarch packages to noarch/ paths) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple