Re: More control over 'make dist'

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,

Re: More control over 'make dist'

On 14.09.2016 21:35, Eric Blake wrote: > [re-adding Michal; not sure he is a subscriber. It's usually best to > reply-to-all rather than assume that all readers are on-list] Thank you, I'll use your e-mail to reply to previous ones too. > > On 09/14/2016 02:10 PM, Warren Young wrote: >> On Sep

Re: More control over 'make dist'

[re-adding Michal; not sure he is a subscriber. It's usually best to reply-to-all rather than assume that all readers are on-list] On 09/14/2016 02:10 PM, Warren Young wrote: > On Sep 14, 2016, at 7:49 AM, Peter Rosin wrote: >> >> On 2016-09-14 11:33, Michal Privoznik wrote:

Re: More control over 'make dist'

On Sep 14, 2016, at 7:49 AM, Peter Rosin wrote: > > On 2016-09-14 11:33, Michal Privoznik wrote: >> >> ln -s $xml.in $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

Re: More control over 'make dist'

On 2016-09-14 11:33, 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

More control over 'make dist'

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