Re: [RFC/P] Port System Re-Engineering (Repost from -ports@)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Aryeh M. Friedman <aryeh.friedman@...>
Cc: <freebsd-current@...>, <freebsd-stable@...>, <freebsd-questions@...>
Date: Monday, December 3, 2007 - 6:56 pm

On Mon, Dec 03, 2007 at 09:19:15AM -0500, Aryeh M. Friedman wrote:

Yes.  (i.e., mu)


Slightly more than weekly.  Updating.


Most of what I want to use is in there, and builds and installs without
fault or clashes.


A toss-up between
- inability to cross-build (not entirely fixable by ports, I
  know, but I'm sure that *some* ports would be buildable with
  appropriate cross-tools, and there's some chance that that set
  would include the pieces I'm interested in...) and
- library dependencies don't extend to the base system.  I've just spent a
  week un-breaking my GNOME environment after upgrading to 7-STABLE from
  6-STABLE (which worked, as did all my existing ports) and then
  portupgrading (which broke nearly everything, because of the upgraded
  system libc.so, libz.so and libpthread.so->libthr.so, resulting in
  applications that depended on both old and new base libraries).  A
  corollary of this is that portupgrade -af is not restartable if
  something breaks or requires manual intervention, which results in
  quadratic rebuild time, unless the whole process is managed manually.


No idea.  I haven't been a new FreeBSD user for a long time.  If I were a
new UNIX user, I might hope that things would work as they do in MacOS-X,
and probably would prefer to use a GUI interface to pre-built packages,
rather than the ports system at all.  [That being the case, it's *most*
important that the ports system be useful for the package-building farm.]


Probably, but there are other aspects of ports that I like.  I *like* that
it's made out of make, and can be coerced into doing things *my* way, with
little effort.  At least I have the fall-back of using the NetBSD pkgsrc
system.  It is mostly Ports with some additional sophistication for
portability.


No.  If you break 3, you lose me to pkgsrc.


FreeBSD since '94, BSD since '85 or '86.


Workstation (software dev.), production CVS/Perforce/Web server,
experimental audio server.


Ports.


1 (it has a user interface?)


8

8


4 (this is only a performance issue)


mu (without having seen the discussion, I don't understand the question.)


Competent.

Cheers,

-- 
Andrew
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC/P] Port System Re-Engineering (Repost from -ports@), Aryeh M. Friedman, (Mon Dec 3, 10:19 am)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Erik Cederstrand, (Tue Dec 4, 5:41 am)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Andreas Pettersson, (Mon Dec 3, 7:35 pm)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Patrick M. Hausen, (Wed Dec 5, 2:05 am)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Philip M. Gollucci, (Mon Dec 3, 9:12 pm)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Andrew Reilly, (Mon Dec 3, 6:56 pm)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), John Merryweather Cooper, (Mon Dec 3, 11:59 am)
Re: [RFC/P] Port System Re-Engineering (Repost from -ports@), Aryeh M. Friedman, (Mon Dec 3, 10:54 am)