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.194.249.134 with SMTP id yu6mr456029wjc.1.1412678822789; Tue, 07 Oct 2014 03:47:02 -0700 (PDT) X-BeenThere: supmua@googlegroups.com Received: by 10.152.6.100 with SMTP id z4ls670177laz.60.gmail; Tue, 07 Oct 2014 03:47:02 -0700 (PDT) X-Received: by 10.112.163.39 with SMTP id yf7mr456408lbb.7.1412678822272; Tue, 07 Oct 2014 03:47:02 -0700 (PDT) Return-Path: Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [2a00:1450:400c:c00::22c]) by gmr-mx.google.com with ESMTPS id p7si127784wiz.1.2014.10.07.03.47.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 03:47:02 -0700 (PDT) Received-SPF: pass (google.com: domain of avtobiff@gmail.com designates 2a00:1450:400c:c00::22c as permitted sender) client-ip=2a00:1450:400c:c00::22c; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of avtobiff@gmail.com designates 2a00:1450:400c:c00::22c as permitted sender) smtp.mail=avtobiff@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Received: by mail-wg0-x22c.google.com with SMTP id y10so8843920wgg.15 for ; Tue, 07 Oct 2014 03:47:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RRoiRU0op7fWSUdFhRDrFSyJrbU/jdvzuCtuCin7bIE=; b=snk635lIUs0FnHfPxyFmmOtLRsBscWTv//TEkzWAsNQ4EkVMY600u9/GpbVyRGpOdN K4a4avXEl2OK+do9JpK18pl8xoLe3vw9aoqv9bLnnez5nG+23NOwMW7K30ZkS8tbPFFD 7y0+R4E3w3KU0m/3/CwqAQ6cNc4G42fuWY6gywFYuo8Y5b3aWw1opdTuI5223Vso5sFh fFitk+F8oi+rhOIkRUDwhj/XPFhf74FZfR/7GDT6zBlHYdB96aum1nLgwNJqK/H7bOR8 0fIe4LVHPUWaaswA8nVkUVqOtRDHIPYC8AAozmuvnTr0VjMYa5jrOmJYP8elZl1lKubX 0Epg== MIME-Version: 1.0 X-Received: by 10.194.123.200 with SMTP id mc8mr3754816wjb.96.1412678822164; Tue, 07 Oct 2014 03:47:02 -0700 (PDT) Received: by 10.27.51.136 with HTTP; Tue, 7 Oct 2014 03:47:02 -0700 (PDT) In-Reply-To: <1412676016-astroid-0-teg6538fjs-12315@strange> References: <1412676016-astroid-0-teg6538fjs-12315@strange> Date: Tue, 7 Oct 2014 12:47:02 +0200 Message-ID: Subject: Re: Generate man pages before dist (WAS Re: [sup] Release 0.20.0) From: Per Andersson To: Gaute Hope Cc: "supmua@googlegroups.com" Content-Type: text/plain; charset=UTF-8 On Tue, Oct 7, 2014 at 12:03 PM, Gaute Hope wrote: > Excerpts from Per Andersson's message of October 7, 2014 11:56: > (...) >>> >>> We've got man pages (Mr. Andersson)! >> >> >> Is it possible to generate the man pages upon release and commit them >> to, say, docs/man. >> >> 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.) >> >> 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? Ah, clever. I like to use the actual upstream source myself though. I'll just build and ship them in the Debian package. -- Per