Old ports bugs analyzis

Arseny Nasokin eirnym at gmail.com
Wed Mar 31 10:28:48 UTC 2010

On 31 Mar 2010, at 12:39, Garrett Cooper <yanefbsd at gmail.com> wrote:
>> If we are talk about specialized optimisations or customisations we  
>> should
>> talk about ports system. If we talk about desktop machines, there  
>> binary
>> packages are better in most cases (for example, using Synaptics  
>> frontend)
> YMMV, but most of the time binary packages are built with the idea in
> mind that it will meet the majority of the end-users' needs instead of
> a specific case (unless there is a good reason for there being
> variance, in that case ports are split, i.e. vim, vim-lite, etc).
> There is a small amount of optimization that can be gained by using
> proper CFLAGS as well with more modern hardware (let's face it.. the
> default flags that binary packages are built with are meant to run on
> generic old-school IBM clones all the way up to the most bleeding edge
> AMD and Intel processors for instance) -- so if you use the
> appropriate CPUTYPE and CFLAGS you can gain performance wise, because
> you're tailoring the programs you compile to meet your system's
> capabilities. You just have to be careful because ricing is something
> that Gentoo users got themselves in trouble with back around 2003 ~
> 2004, and then I think that most people learned that they weren't
> really gaining much in performance and were losing in stability, so
> they stopped ricing their compiles.
> Cheers,
> -Garrett

I've talked about custom built-in settings. Different options are need  
in different situations. We doesn't have any real statistics about  
options use.

For example, gvim(1) is good idea on most desktop systems, but after  
some issue, I build vim without GUI support. Issue is simple:

Start x11, run xterm, run screen in it, detach, shutdown x11 server.  
Attach to screen from text mode and run vim. You'll get at least  
warning and slow startup.
Second issue about is why should X11 be on headless server?

What should we do in this case? Create 10-20 packages for every  
program? Or provide customisation interface (ports tree)?

If second we can provide ports tree, which can download prebuild  
package if common options are used or build it in other case or if  
user want it. 

More information about the freebsd-ports mailing list