cvs commit: src/lib/libc/locale utf8.c
obrien at FreeBSD.org
Mon Oct 29 09:02:23 PDT 2007
On Sat, Oct 27, 2007 at 11:57:05PM +0200, Kris Kennaway wrote:
> David O'Brien wrote:
>> On Fri, Oct 26, 2007 at 05:46:09PM -0400, Ken Smith wrote:
>>> On Fri, 2007-10-26 at 13:30 -0700, David O'Brien wrote:
>>>> On Fri, Oct 26, 2007 at 02:47:13PM -0400, Ken Smith wrote:
>>>>> If portmgr@ uses RELENG_6 to base their builds on breaking forward
>>>>> compat would mean all consumers of packages-6-stable would also
>>>>> need to use RELENG_6.
>>>> When did this sease being a requirement?
>>>> 'pkg_add -r' certainly enforces this requirement. `pkg_add -r jive'
>>>> on 6.2-RELEASE will always pull from the packages-6.2-release/ and
>>>> not packages-6-stable/.
>>> I thought you could use portupgrade on a 6.2-REL system and have it
>>> pull the packages from a packages-6-stable tree.
>> This is not the case for 'portupgrade -P[P]':
[ pkgtools.rb code snipped ]
> portupgrade uses the same environment variables that pkg_add does that
> allow the user to override the default to packages-6-stable/. Many
> users do this.
And they could also symlink libc.so.6 to libc.so.7, set PACKAGESITE to
specify packages-7-current and 'pkg_add -r'. Many, many things will work
fine. But that doesn't mean we guarentee it will work in all cases.
Folks are lucky where it works (using X-stable packages on X-release),
but its not something we can garentee unless we want -stable to be
-- David (obrien at FreeBSD.org)
More information about the cvs-all