Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Jul 2015 11:47:42 +0100
From:      David Chisnall <theraven@FreeBSD.org>
To:        Vsevolod Stakhov <vsevolod@FreeBSD.org>
Cc:        marino@freebsd.org, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org
Subject:   Re: svn commit: r391493 - head/cad/tkgate
Message-ID:  <15B6E028-2BD8-4E72-BD6E-BEC2ACBD4929@FreeBSD.org>
In-Reply-To: <559BACBB.2030308@FreeBSD.org>
References:  <201507070635.t676Zaqw085725@repo.freebsd.org> <559B9C36.2060300@FreeBSD.org> <559BA1B2.4050002@marino.st> <559BA55C.2080701@FreeBSD.org> <A3950497-8237-43F1-BC01-76194028D662@FreeBSD.org> <559BAA0F.4030509@FreeBSD.org> <53EEEF45-07F5-4EFF-847D-C31B53917A70@FreeBSD.org> <559BACBB.2030308@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7 Jul 2015, at 11:40, Vsevolod Stakhov <vsevolod@FreeBSD.org> wrote:
>=20
> I'm trying to say that's it's a bad practice to prefer base system
> dependencies for the ports software.

I disagree.

> By nature, the ports are the
> rolling release of software where we have the most recent versions of
> software. Isn't it sane to prefer dependencies on the software
> installed from the ports as well?

By that logic, we should have a version of libc and all other libraries =
in /usr/lib in ports, do rolling releases of them, and never have any =
dependencies on anything in the base system from ports software.

> This would also allow to upgrade
> software easily (including security fixes, for example).

The real problem is that upgrading the base system is harder than =
upgrading ports.  The fix for this is to make upgrading the base system =
easier, not to remove all uses of the base system.

David




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15B6E028-2BD8-4E72-BD6E-BEC2ACBD4929>