From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#24105: git package misses man pages Date: Fri, 29 Jul 2016 13:10:59 -0400 Message-ID: <20160729171059.GA14354@jasmine> References: <20160729124623.GA31006@solar> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45647) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bTBKT-0005WF-Bt for bug-guix@gnu.org; Fri, 29 Jul 2016 13:12:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bTBKO-0004zy-Hf for bug-guix@gnu.org; Fri, 29 Jul 2016 13:12:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:53593) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bTBKM-0004za-6c for bug-guix@gnu.org; Fri, 29 Jul 2016 13:12:04 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bTBKM-0007wI-1c for bug-guix@gnu.org; Fri, 29 Jul 2016 13:12:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20160729124623.GA31006@solar> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Andreas Enge Cc: 24105@debbugs.gnu.org On Fri, Jul 29, 2016 at 02:46:23PM +0200, Andreas Enge wrote: > Also, the resulting package is quite small with only 2.3 MB. Not much, considering how often I consult these manpages. > The reason for the separate package is given as this: > ;; Granted, we could build the man pages from the 'git' package itself, > ;; which contains the real source. However, it would add a dependency on a > ;; full XML tool chain, and building it actually takes ages. So we use this > ;; lazy approach. > Building will most of the time happen on the build farm, so the time it > takes should not be an issue. I suppose that the xml tool chain will only > be a native and not a normal input, so it should not be too much of a problem. Our git-manpages package doesn't build the manpages from source anyways. It simply unpacks a tarball of pre-built manpages. > I suggest to include the man pages into the git package itself. If building > them is a real issue, adding a source and the build phase of git-manpages > to the git package itself could also be an option. I agree. If we continue to not build them from source, it won't make the Git package any more "expensive". We could add the pre-built source tarball as a native-input to the Git package, and re-use the unpack phase from git-manpages. I think the current arrangement offers a bad experience for new users who can't find the manpages.