Date: Sat, 21 Apr 2007 10:37:57 -0700 From: David Southwell <david@vizion2000.net> To: freebsd-ports@freebsd.org Cc: Paul Schmehl <pauls@utdallas.edu> Subject: Re: Mailman GID problem Message-ID: <200704211037.58385.david@vizion2000.net> In-Reply-To: <6B5244E71ECEF8A4BEB18D16@paul-schmehls-powerbook59.local> References: <200704200842.48793.david@vizion2000.net> <200704210333.08947.david@vizion2000.net> <6B5244E71ECEF8A4BEB18D16@paul-schmehls-powerbook59.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 21 April 2007 08:50:41 Paul Schmehl wrote: > --On April 21, 2007 3:33:08 AM -0700 David Southwell > > <david@vizion2000.net> wrote: > > Lastly the standard make ./configure does not work with mailman neither > > is there a record available which enables one to check the current > > settings including GID applicable to the installed version. This means > > that when an attempt is made to apply an option and the make does not > > do so there is no way one can tell!! > > If you just do make in a port (instead of make install clean), you should > have all the usual stuff in the working directory, including the results > of configure. In fact, as long as you don't do make clean, the working > directory remains, along with everything you would expect to find in a > ./configure, make, make install scenario. When things are going well I might be tempted to not make clean but when, quite clearly, something is not right with the port then why would not one make clean? Am I being unreasonable to suggest that it is good practice to have a means of determining the values of the current running configuration quite independently of the directory used for compile purposes? david
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704211037.58385.david>