From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 272424239104 X-Google-Groups: supmua X-Google-Thread: 3030fda1bf,18a57e4611533136 X-Google-Attributes: gid3030fda1bf,domainid0,public,googlegroup X-Google-NewGroupId: yes X-Received: by 10.112.205.70 with SMTP id le6mr426544lbc.4.1412676190153; Tue, 07 Oct 2014 03:03:10 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.152.43.103 with SMTP id v7ls702539lal.32.gmail; Tue, 07 Oct 2014 03:03:09 -0700 (PDT) X-Received: by 10.112.190.40 with SMTP id gn8mr313024lbc.10.1412676189439; Tue, 07 Oct 2014 03:03:09 -0700 (PDT) Return-Path: Received: from mail-la0-f49.google.com (mail-la0-f49.google.com [209.85.215.49]) by gmr-mx.google.com with ESMTPS id us10si1894292lbc.1.2014.10.07.03.03.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 03:03:09 -0700 (PDT) Received-SPF: none (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) client-ip=209.85.215.49; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: eg@gaute.vetsj.com does not designate permitted sender hosts) smtp.mail=eg@gaute.vetsj.com Received: by mail-la0-f49.google.com with SMTP id q1so5874687lam.8 for ; Tue, 07 Oct 2014 03:03:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:subject:to:references:in-reply-to :user-agent:message-id:mime-version:content-type :content-transfer-encoding; bh=ddiija4hbyAQBAkm86jV6+TviLCaHKYqzQnGvNM9PSY=; b=fYh6glFIEePImKrDkuVC6/uRyFFRWk+b8iqaUzfoSny0AhpyLlv8853L1XIlkr6+TE W2d3fDlL40y8ItVvXMK+g4plvZr28dk99CYx7Z0DMmpmRJFGwoqzfbp/LjHa/fAGhhVk QTHlhsZlCarZ4G/+7jDO4h99gv2IQHM/dvQN4kXL3PUYRO4EpJeHXuC3oUyW1lT3NqhS buir08hxjZnisLlaRVGaJ5AJh+vk+mZG1XfTE7HH/XpS1fA/yMo9AHHC45Bg0kngifLk +uxB9JEI5/1+kSPZBrfKnZonmiikCRUm2948qYk8T5gMLOtTqvHebjT6bE/PwK1hgyPo cSbg== X-Gm-Message-State: ALoCoQkIcl2A7+fMpAfgayvGtH0PC9YeXSRJgZUNL/MH16NAp70RGmAoeNPKHHKAslYZLLGM9rdj X-Received: by 10.112.135.230 with SMTP id pv6mr2006819lbb.105.1412676188840; Tue, 07 Oct 2014 03:03:08 -0700 (PDT) Return-Path: Received: from localhost (cD572BF51.dhcp.as2116.net. [81.191.114.213]) by mx.google.com with ESMTPSA id x6sm3266521lbj.40.2014.10.07.03.03.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Oct 2014 03:03:08 -0700 (PDT) Date: Tue, 07 Oct 2014 10:03:46 +0000 From: Gaute Hope Subject: Re: Generate man pages before dist (WAS Re: [sup] Release 0.20.0) To: supmua@googlegroups.com, Per Andersson References: In-Reply-To: User-Agent: astroid/vb457ef13 (https://github.com/gauteh/astroid) Message-Id: <1412676016-astroid-0-teg6538fjs-12315@strange> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Excerpts from Per Andersson's message of October 7, 2014 11:56: > Hi! >=20 > On Mon, Oct 6, 2014 at 10:07 PM, Gaute Hope wrote: >> Hi suppers! >> >> Sup 0.20.0 has been released! Go get it at rubygems: >=20 > \o/ >=20 >=20 >> $ gem install sup >> >> The news are as follows: >> >> We've got man pages (Mr. Andersson)! >=20 > Is it possible to generate the man pages upon release and commit them > to, say, docs/man. >=20 > That would make the Debian packaging much simpler, otherwise I have > to do that myself manually and put them in the debian directory. (It will > probably be easy to miss shipping updated man page in the Debian > package.) >=20 > Debian packages should be buildable without network access, so using > the git submodule at build time will not work. The man files should be included in the man/ directory in the gem. You can check out the contents of the built gem by unpacking it manually: $ tar xf sup-0.20.0.gem $ tar xf data.tar.gz so all necessary files for a release should be included. I would suggest starting the source build off the .gem with the pre-generated man pages. Does that work for you? Cheers, Gaute =