----- Original Message -----
From: "Alon Bar-Lev" <alonbl(a)redhat.com>
To: "Federico Simoncelli" <fsimonce(a)redhat.com>
Cc: vdsm-devel(a)lists.fedorahosted.org, "Itzik Brown"
<ItzikB(a)mellanox.com>
Sent: Thursday, September 20, 2012 12:41:58 PM
Subject: Re: [vdsm] Problem building vdsm RPM
----- Original Message -----
> From: "Federico Simoncelli" <fsimonce(a)redhat.com>
> To: "Alon Bar-Lev" <alonbl(a)redhat.com>
> Cc: vdsm-devel(a)lists.fedorahosted.org, "Itzik Brown"
> <ItzikB(a)mellanox.com>
> Sent: Thursday, September 20, 2012 1:38:23 PM
> Subject: Re: [vdsm] Problem building vdsm RPM
>
> The problem with your rpmbuild command is that it's not automatic
> enough,
> if you want to automate it you use wildcards (vdsm*.gz) which will
> build
> any vdsm tar.gz you find in the directory rather the one you just
> prepared
> (which is what make rpm is doing).
>
> It's not that what you're saying is wrong (after all it's what
> autogen.sh
> and the Makefile rely upon, and it works for you), it's that what
> you
> do
> manually is already done automatically (with less potential errors
> and
> confusion for the newcomers).
Well, my view is that there is a standard method of creating rpms out
of source tree.
That is why I pushed for autotools, so experienced people can use it in
all the way they prefer.
Newcomers that have done this on one project can reuse their
knowledge to do this in another project.
There is no need to create custom unique methods to confuse people.
Are you suggesting that "./autogen.sh && make rpm" is
"unique"?
--
Federico