----- Original Message -----
> From: "Federico Simoncelli" <fsimo...@redhat.com>
> To: "Alon Bar-Lev" <alo...@redhat.com>
> Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown" <itz...@mellanox.com>
> Sent: Thursday, September 20, 2012 2:15:58 PM
> Subject: Re: [vdsm] Problem building vdsm RPM
> 
> ----- Original Message -----
> > From: "Alon Bar-Lev" <alo...@redhat.com>
> > To: "Federico Simoncelli" <fsimo...@redhat.com>
> > Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown"
> > <itz...@mellanox.com>
> > Sent: Thursday, September 20, 2012 12:41:58 PM
> > Subject: Re: [vdsm] Problem building vdsm RPM
> > 
> > ----- Original Message -----
> > > From: "Federico Simoncelli" <fsimo...@redhat.com>
> > > To: "Alon Bar-Lev" <alo...@redhat.com>
> > > Cc: vdsm-devel@lists.fedorahosted.org, "Itzik Brown"
> > > <itz...@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"?
> 

Well... as far as I know more common is:
$ ./autogen
$ ./configure
$ make rpm

While I don't see the "make rpm" is required, I do not really care, as far as 
there is no magic hidden within... so that when we will publish release 
tarballs for download (using make dist of course no magic), people can simply 
do rpmbuild -tb on these to produce valid rpms.

In the past people needed to use aclocal, autoconf, libtool, automake, gettext 
in proper sequence in order to produce build environment. autogen(or any 
script) was born to automate this task, the task of producing build environment 
so that configure could be executed.

These days a single 'autoreconf -ivf' is doing exactly what in the past was 
complex, hence no autogen is required any more... but I don't care project 
putting a single command just for keep the name...

Thanks,
Alon.
_______________________________________________
vdsm-devel mailing list
vdsm-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel

Reply via email to