inn-2.4.3 - need comments and testing

Hi ports@, I'm almost done with the inn port except that: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ? 2- this one being my first port, I probably did some thing(s) wrong,

small x264 change

Hi. This diff makes multimedia/x264: - really use nasm for building under i386 - use yasm support for building under amd64 - don't automatically add -fPIC to $CFLAGS (we take care of this in the Makefile so that libx264.a can be built from non pic objects). Comments/OK? -- Antoine Index:

Re: inn-2.4.3 - need help

On Thu, Jul 19, 2007 at 12:47:56PM -0500, Gilles Chehade wrote: I realized that inn wasn't the best choice for a first port just a minute ago when I looked at the clock and noticed that I've spent two evenings on what was supposed to take me just a few hours ... Oh well ... now that I'm

Re: inn-2.4.3 - need comments and testing

On Thu, Jul 19, 2007 at 11:54:18PM -0500, Gilles Chehade wrote: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ? You mean during fake stage? Well, the user is created add install

Re: inn-2.4.3 - need comments and testing

On Fri, Jul 20, 2007 at 06:01:42PM +0200, Matthias Kilian wrote: On Thu, Jul 19, 2007 at 11:54:18PM -0500, Gilles Chehade wrote: 1- even though the PLIST starts with @newuser, the user does not get created and I am forced to create it manually. Anyone can explain what I do wrong ?

Re: inn-2.4.3 - need comments and testing

On Fri, Jul 20, 2007 at 05:25:27AM -0500, Gilles Chehade wrote: ksh: }fmt: not found floating around the archives), especially on patch-support_install-sh. Unfortunately, Deannas port seems to be unavailable. I don't get that :-) Argh! I garbled my own mail. Sorry. That should read

Re: ports(7) inconsistent with bsd.port.mk(5) on FORCE_UPDATE?

I can understand if no-one wants to take the time to explain this, but could someone just tell me if I should go re-read the man-pages or if there actually are something wrong in ports(7)? Thanks. BR, Markus Markus Bergkvist wrote: Hi, I'm not sure I understand this correct, but to me it

Re: ports(7) inconsistent with bsd.port.mk(5) on FORCE_UPDATE?

On 2007/07/20 23:22, Markus Bergkvist wrote: I can understand if no-one wants to take the time to explain this, but could someone just tell me if I should go re-read the man-pages or if there actually are something wrong in ports(7)? ports(7) is user docs, FORCE_UPDATE=hard is really useful

Re: ports(7) inconsistent with bsd.port.mk(5) on FORCE_UPDATE?

Fair enough. But shouldn't ports(7) say something like If FORCE_UPDATE is set to `Yes', dependencies will also be updated first, and packages will be updated, as soon as there is a difference between the old and the new packages. (with some grammar and allusion corrections perhaps) to

Re: ports(7) inconsistent with bsd.port.mk(5) on FORCE_UPDATE?

On 2007/07/21 00:17, Markus Bergkvist wrote: Fair enough. But shouldn't ports(7) say something like If FORCE_UPDATE is set to `Yes', dependencies will also be updated first, and packages will be updated, as soon as there is a difference between the old and the new packages. (with some

simplification of the FLAVORs defined for mutt

Here is a diff based on a suggestion Todd had and that is to integrate the compressed and sidebar FLAVORs by default, as they do not introduce any new external dependencies. As well as a little cleanup. Todd has tested that the various combinations of FLAVORs currently in the port build Ok.

UPDATE: multimedia/ffmpeg2theora (0.19)

Hi, attached is an update for the ffmpeg2theora port. Port changes: * Update from 0.17 to 0.19 * Change MAINTAINER email Ffmpeg2theora changes: * Documentation improvements * New option -Z/--saturation * Support output 2GB on 32bit archs * Fix short option -k * Some other new things