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:references:cc:to:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=ozjujLhY+sLVblyW vqTMdqfg/tURB3+0ZuASOJx5rolFht2fjF4w4eukphtz50u0oQmFJtaaYrlh/iFI 9uT38XMxpY6YGjgHjDRttuXgeEzJURGXHi6Lg3GIZD8/4PTOrzs7Hw6gLIu8hwBv OT5SKpAMdRjmeJUXvY1R7Wg8Azs= 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:references:cc:to:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=B1CbaSgmgo2FStnjREf+fk D5RwY=; b=ki3hQ/R0zYB23YRJVHfQE29uF9Lzd0X0ZlN4Jwqdwl7a80fJBhYkfb nGDK8U2j7MWNRUp+R6fUOMRB8LFz1WQxRADZhNqOQLBaWQZLJxTXN/66nwn7lW+Y sYsFDAAcyNMeRxwjB6H3LQU03uqu5GHTeidF/rzD6RP9jDj0rv9g4= 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=-3.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Choose, gagis, Gagis, H*i:sk:1073a24 X-HELO: out1-smtp.messagingengine.com X-ME-Sender: Subject: Re: Setting up overlay package server References: <1073a24a-e21c-53c8-ae34-92f485616f5b AT gmail DOT com> Cc: Ivan Gagis To: The Cygwin Mailing List From: Jon Turney Message-ID: Date: Sat, 25 Mar 2017 13:15:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1073a24a-e21c-53c8-ae34-92f485616f5b@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 25/03/2017 10:55, Ivan Gagis wrote: > Hi, > > I'm developing some software which consists of several libraries and I > would like to distribute it for Cygwin. So, I would need a feature of > setting up a custom cygwin repository for my packages. As I understand > the most suitable here would be an overlay package server. Right? > > Unfortunately, I could find no information on the web about how to set > up an overlay package server. Cygwin page > https://cygwin.com/package-server.html misses the docs about how to do > that also, saying that the manual is TBD. So, is it very complicated to > do that, so that even manual is not yet written? No, it's not that complicated. > Are there any plans to complete the manual about setting up the overlay > package server? The plan is to do it when someone gets around to it :) As it says on that page, "If you can help update this documentation, please send corrections to the cygwin-apps mailing list." > Could somebody give me some hints on how to do that? Follow the steps of "creating a custom Cygwin package server", but instead of copying/linking an existing Cygwin mirror in step 2, start with an empty directory. In step 3, add the '-okmissing=required-package' flag to mksetupini (this turns off checking that all dependencies can be found, since presumably some of them will be provided by the standard Cygwin package repository. (See footnote 1) (Additionally, if you are going to overlay an existing package with a test: version in your repository, you will need to use the '--okmissing=curr' flag to indicate that it's ok not to have a curr: version of a package) > And what would be the configurations needed on the user side to start > using my overlay server? Ideally, I'd prefer it would be working with > apt-cyg script. With cygwin setup, you will need to *add* the URL of your repository. On the "Choose A Download Site" page, enter the URL of your repository in the "User URL" box, press "Add". Then ensure *both* that site *and* a Cygwin mirror site are selected. I can't help you with apt-cyg. (footnote 1): We are currently lacking a tool to check that cross-repository dependencies can be satisfied (i.e. that packages for these presumptive dependencies actually exist), so you should run setup, tell it to install *everything*, and see if the "Resolving dependencies" page reports any dependencies as not found. (See discussion starting at [1]) [1] https://cygwin.com/ml/cygwin-apps/2016-07/msg00007.html -- 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