Re: [vchkpw] Test FHS patch

2009-04-03 Thread Matt Brookings
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 aledr wrote: Here it is! Do not worry about the RPM errors at the end, I need to fix It on my spec file. You will need to also package in the vusage daemon. It's basically a requirement for the 5.5 tree. It's just not required when building

Re: [vchkpw] vpopmail make install should support DESTDIR

2009-04-03 Thread John Simpson
On 2009-04-01, at 1306, Matt Brookings wrote: John Simpson wrote: this should make it possible to not require root in order to configure or build the software... or is there some other reason root permissions are required? They are required because currently, the Makefiles want to mkdir

Re: [vchkpw] vpopmail make install should support DESTDIR

2009-04-03 Thread John Simpson
On 2009-04-01, at 1356, Manvendra Bhangui wrote: On Wed, Apr 1, 2009 at 9:41 PM, John Simpson j...@jms1.net wrote: the only problem i see at the moment is how the FHS stuff is going to affect where the files are. i want the program to self-adjust to FHS layout or built from source layout

Re: [vchkpw] vdelivermail stdout to Dovecot deliver

2009-04-03 Thread Rick Romero
On Thu, 2009-04-02 at 06:01 -0700, Tom Collins wrote: On Mar 30, 2009, at 7:32 PM, Rick Romero wrote: What I'm trying to work around with this method is to handle user-specific .qmail directives. Dovecot doesn't do that, and that is why I can't full out replace vdelivermail with deliver.

Re: [vchkpw] Further Information for Building RPM for vpopmail

2009-04-03 Thread John Simpson
On 2009-04-02, at 1036, Manvendra Bhangui wrote: 2009/4/2 John Simpson j...@jms1.net you DO NOT want these to be setuid root. in fact, you don't want ANY of the binaries to be setuid root, except possibly for vpopmaild, and that only if you want to allow it to create and remove domains-

Re: [vchkpw] vpopmail make install should support DESTDIR

2009-04-03 Thread Manvendra Bhangui
On Fri, 2009-04-03 at 18:49 -0400, John Simpson wrote: normally the configure command builds a file like config.h, which all of the other source files include. my question was what information is, or will be, available in config.h to tell where the various pieces of the package (i.e.