Re: why vim ports have personal KNOBS for options
On 27/03/2011 21:40, Subbsd wrote: On Sun, Mar 27, 2011 at 10:48 PM, Erik Trulssonertr1...@student.uu.se wrote: On Sun, Mar 27, 2011 at 10:19:44PM +0400, Subbsd wrote: Ive wanted to ask why the option of vim port has not yet been handed via dialog by default. Personally, to make them work, we must define WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without it is so difficult ;) Because the maintainer of the vim port has a dislike for the OPTIONS framework. I expected to hear that just so happened historically. Тext question I ask only to satisfy my interest. What OPTIONS framework basically can someone not like it? Цhat are the disadvantages compared to grep define /usr/ports/category/portname/Makefile ? Maybe the other of thousand maintainrs something not know about it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org bapt@ made a proposal to improve the OPTION framework and it will be reviewed by portmgr@ soon. This will include a improvment that obrien@ disliked much : when you have WITHOUT_NLS=true in your /etc/make.conf any port that use OPTIONS framework will not honour this knob and this is obviously painful. The bapt@ patch correct this, so the the new OPTION framework will read these KNOBS (but of course there is more coming) Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: why vim ports have personal KNOBS for options
On Sun, Mar 27, 2011 at 10:19:44PM +0400, Subbsd wrote: Ive wanted to ask why the option of vim port has not yet been handed via dialog by default. Personally, to make them work, we must define WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without it is so difficult ;) Because the maintainer of the vim port has a dislike for the OPTIONS framework. -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: why vim ports have personal KNOBS for options
On Sun, Mar 27, 2011 at 10:48 PM, Erik Trulsson ertr1...@student.uu.se wrote: On Sun, Mar 27, 2011 at 10:19:44PM +0400, Subbsd wrote: Ive wanted to ask why the option of vim port has not yet been handed via dialog by default. Personally, to make them work, we must define WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without it is so difficult ;) Because the maintainer of the vim port has a dislike for the OPTIONS framework. I expected to hear that just so happened historically. Тext question I ask only to satisfy my interest. What OPTIONS framework basically can someone not like it? Цhat are the disadvantages compared to grep define /usr/ports/category/portname/Makefile ? Maybe the other of thousand maintainrs something not know about it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: why vim ports have personal KNOBS for options
I expected to hear that just so happened historically. Тext question I ask only to satisfy my interest. What OPTIONS framework basically can someone not like it? http://lists.freebsd.org/pipermail/freebsd-ports/2010-October/063914.html -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
