You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Paul Querna <ch...@force-elite.com> on 2004/06/24 03:17:08 UTC

buildconf on CVS Snapshots

Is it possible to have buildconf be run on the server when the CVS
Snapshots are made of httpd-2.0?

This is a common practice for open source projects with their CVS
snapshots, and removes extra dependencies on autofoo for users.

Thanks,

-Paul Querna


Re: buildconf on CVS Snapshots

Posted by Paul Querna <ch...@force-elite.com>.
On Wed, 2004-06-23 at 20:18 -0700, Sander Temme wrote:
> On Jun 23, 2004, at 6:17 PM, Paul Querna wrote:
> 
> > Is it possible to have buildconf be run on the server when the CVS
> > Snapshots are made of httpd-2.0?
> >
> > This is a common practice for open source projects with their CVS
> > snapshots, and removes extra dependencies on autofoo for users.
> 
> The problem with that, for us, is that the CVS server machine runs 
> FreeBSD and has GNU libtool installed from the ports collection. The 
> FreeBSD ports collection has a really old version of libtool (1.3.4), 
> which is broken for many platforms.

Try /usr/ports/devel/libtool14

I use it on serveral FreeBSD machines for Apache and Module Development,
without any problems.

>  An option would be to install an 
> autotoolset of the level that we require/like, say in /usr/local/gnu, 
> and prepend its bin to the PATH for roll operations. That would give us 
> a known autotoolset for releases/drops instead of what the RM happens 
> to have on their machine.

I like that better. Give a very controlled environment for making
releases, so that they are all consistent.

-Paul Querna


Re: buildconf on CVS Snapshots

Posted by Sander Temme <sa...@temme.net>.
On Jun 23, 2004, at 6:17 PM, Paul Querna wrote:

> Is it possible to have buildconf be run on the server when the CVS
> Snapshots are made of httpd-2.0?
>
> This is a common practice for open source projects with their CVS
> snapshots, and removes extra dependencies on autofoo for users.

The problem with that, for us, is that the CVS server machine runs 
FreeBSD and has GNU libtool installed from the ports collection. The 
FreeBSD ports collection has a really old version of libtool (1.3.4), 
which is broken for many platforms. An option would be to install an 
autotoolset of the level that we require/like, say in /usr/local/gnu, 
and prepend its bin to the PATH for roll operations. That would give us 
a known autotoolset for releases/drops instead of what the RM happens 
to have on their machine.

Of course I don't know that those snapshots are rolled on the CVS 
box... I could be smoking crack.

S. (Hmmm... Crack...)

-- 
sander@temme.net              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF