Return-Path: Received: from smtp.stanford.edu (smtp1.Stanford.EDU [171.67.219.81]) by krbdev.mit.edu (Postfix) with ESMTP id B1EB6CCA09 for ; Sat, 12 Sep 2009 18:27:47 +0000 (UTC) Received: from smtp.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 8C7571783CE for ; Sat, 12 Sep 2009 11:27:46 -0700 (PDT) Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.67.225.134]) by smtp.stanford.edu (Postfix) with ESMTP id 4E7E717829E for ; Sat, 12 Sep 2009 11:27:46 -0700 (PDT) Received: by windlord.stanford.edu (Postfix, from userid 1000) id 0C7972F405; Sat, 12 Sep 2009 11:27:46 -0700 (PDT) From: Russ Allbery To: rt@krbdev.mit.edu Subject: Re: [krbdev.mit.edu #6561] No option to only build client and libs In-Reply-To: (rt-comment@krbdev.mit.edu's message of "Sat, 12 Sep 2009 16:57:55 +0000 (UTC)") Organization: The Eyrie References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Date: Sat, 12 Sep 2009 11:27:46 -0700 Message-ID: <874or8yq59.fsf@windlord.stanford.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii RT-Send-Cc: X-RT-Original-Encoding: us-ascii Content-Length: 1126 "ohnobinki@ohnopublishing.net via RT" writes: > The distribution's task of making certain features of your package > optional is somewhat dependent on your buildsystem's support for such. > If every single distribution which packages mit-krb5 has to generate and > maintain its own patches to the mit-krb5 buildsystem to have conditional > building support, effort is wasted. Also, if your buildsystem builds > programs which the distribution isn't installed, the user has to wait > for those portions to be built. Thus, I think the proper place to > implement conditional building and installation is within your > buildsystem. I suspect this is a Gentoo-specific problem. For Red Hat and Debian at least, and I suspect for all distribution packaging that isn't based on the end-user compiling their own version of the software, there's no need to support building portions of the software. Building Debian packages or RPMs always builds all related packages, and then the user chooses which of those to install. -- Russ Allbery (rra@stanford.edu)