[EMAIL PROTECTED] writes:
Hi.
My dillema:
1) compile docs pre-build-time; or
2) compile docs in build-time
Pros of 1: build-time and Build-Depends
Pros of 2: diff.gz and unnecessary manual intervention of downstream
maintainer (me :) )
So, what are best practices about this?
[EMAIL PROTECTED] writes:
Hi.
My dillema:
1) compile docs pre-build-time; or
2) compile docs in build-time
Pros of 1: build-time and Build-Depends
Cons:
- Docs that can be unbuildable or out of sync with the source.
- Binary files in the diff.gz (have fun with that one) either
* Junichi Uekawa
| Another aspect is maintenance cost. Auto* tools and docbook toolchain,
| and tex toolchain may break, which means packages no longer
| build. This, I believe, shouldn't really be considered a reason not to
| build-depend; because it will be the users who will suffer from a
|
Hi,
It seems like it would be quite taxing on the autobuilders to have to pull
something like docbook (and its chain of dependencies) into a pbuilder
just
to recompile a manpage that doesn't change between architectures.
AIUI, the autobuilders use sbuild and don't purge the
Steinar H. Gunderson skrev:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a reason,
architecture-specific or -independent alike.
That depends a bit
[EMAIL PROTECTED] wrote:
tony mancill [EMAIL PROTECTED] writes:
Steinar H. Gunderson wrote:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a reason,
architecture-specific or -independent alike.
That depends a bit on the stuff. A lot of maintainers think running
auto* to generate configure and
On Tue, Jul 04, 2006 at 09:04:48PM -0300, [EMAIL PROTECTED] wrote:
tony mancill [EMAIL PROTECTED] writes:
Steinar H. Gunderson wrote:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the
On Tue, Jul 04, 2006 at 04:45:21PM -0700, tony mancill wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steinar H. Gunderson wrote:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely
On Tue, Jul 04, 2006 at 09:18:20PM -0400, Roberto C. Sanchez wrote:
tony mancill wrote:
It seems like it would be quite taxing on the autobuilders to have to pull
something like docbook (and its chain of dependencies) into a pbuilder just
to recompile a manpage that doesn't change
On Wed, Jul 05, 2006 at 09:45:16PM +0900, Junichi Uekawa wrote:
Another aspect is maintenance cost. Auto* tools and docbook toolchain,
and tex toolchain may break, which means packages no longer
build. This, I believe, shouldn't really be considered a reason not to
build-depend; because it
Wouter Verhelst wrote:
No, that's not true; packages that are installed at the beginning of a
build run are removed at the end. The main difference between pbuilder
and sbuild is the fact that sbuild uses an existing chroot on which it
works (or even builds in your main system if you have no
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a reason,
architecture-specific or -independent alike.
/* Steinar */
--
Homepage: http://www.sesse.net/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steinar H. Gunderson wrote:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a reason,
tony mancill [EMAIL PROTECTED] writes:
Steinar H. Gunderson wrote:
On Tue, Jul 04, 2006 at 07:25:16PM -0300, [EMAIL PROTECTED] wrote:
1) compile docs pre-build-time; or
2) compile docs in build-time
Definitely the latter. We build stuff at build time for a reason,
architecture-specific
tony mancill wrote:
It seems like it would be quite taxing on the autobuilders to have to pull
something like docbook (and its chain of dependencies) into a pbuilder just
to recompile a manpage that doesn't change between architectures.
AIUI, the autobuilders use sbuild and don't purge the
16 matches
Mail list logo
