[11145] in Kerberos-V5-bugs
Re: [krbdev.mit.edu #6561] No option to only build client and libs
daemon@ATHENA.MIT.EDU (Russ Allbery via RT)
Sat Sep 12 14:28:12 2009
Mail-Followup-To: rt@krbdev.mit.edu
mail-copies-to: never
From: "Russ Allbery via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6561@krbdev.mit.edu>
Message-ID: <rt-6561-31693.2.38712952997936@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6561'":;"'AdminCc of krbdev.mit.edu Ticket #6561'":;@MIT.EDU
Date: Sat, 12 Sep 2009 18:27:48 +0000 (UTC)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
"ohnobinki@ohnopublishing.net via RT" <rt-comment@krbdev.mit.edu> 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) <http://www.eyrie.org/~eagle/>
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
