[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: More control over 'make dist'

From: Daniel Herring
Subject: Re: More control over 'make dist'
Date: Wed, 14 Sep 2016 21:38:02 -0400 (EDT)
User-agent: Alpine 2.11 (DEB 23 2013-08-11)

Hi Michal,

I've always handled this by distributing the single real file, along with a script that creates missing symlinks later, either during configure or as part of one of the make targets.

Its a bit quirky, but not too annoying. Since the dist target is for making source packages, there are plenty of natural places to hide this.

Many related pieces of infrastructure, including Debian packages, have the same basic symlink packing issue and workaround.

- Daniel

On Wed, 14 Sep 2016, Michal Privoznik wrote:

Dear list,

I'm a libvirt devel and I've ran into interesting problem. I'd like to
hear your opinions on it.

Libvirt is a virtualization library that uses XML to store a virtual
machine config. We have couple of tests in our repository too that check
whether XML configs are valid, and whether some operations change it in
expected way. Some operations don't change the XML at all, in which case
we just symlink the output file to point to the input file:

ln -s $ $xml.out

However, I was looking into archive produced by 'make dist' the other
day and found out that the symlinks are not preserved. I've traced down
the problem and found that autoconf is just hardcoding some of tar's
options. Namely -chf. Yes, it is -h that causes a symlink to be

So my question is, what do you think of making -h configurable? We could
add new tar-* option to AM_INIT_AUTOMAKE, say tar-symlinks, which would
suppress -h on tar's command line.

What are your thoughts?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]