Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Sep 2014 11:44:04 +0200
From:      Michelle Sullivan <michelle@sorbs.net>
To:        Florent Peterschmitt <florent@peterschmitt.fr>
Cc:        "ports@freebsd.org" <ports@freebsd.org>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: pkg 1.3.8 requested but not available?
Message-ID:  <542140E4.6050605@sorbs.net>
In-Reply-To: <542138B9.3060600@peterschmitt.fr>
References:  <CAO82ECHfocf=c2=ShbdJSg7Y8sjbQNChNZexzn8XMW6zaPwp=g@mail.gmail.com> <20140923083359.GA20383@ivaldir.etoilebsd.net> <54213713.7020200@sorbs.net> <542138B9.3060600@peterschmitt.fr>

next in thread | previous in thread | raw e-mail | index | archive | help
Florent Peterschmitt wrote:
> Le 23/09/2014 11:02, Michelle Sullivan a écrit :
>   
>> Baptiste Daroussin wrote:
>>     
>>> [...]
>>> You are using portupgrade so first upgrade pkg with portupgrade
>>>
>>>   
>>>       
>> Just a thought here - why (like .rpm and .deb - and the reason I hate
>> them so much) are you making the package manager version a dependency of
>> a package?  I can understand if there are new features that you may need
>> to use a later version to get those features, but making a package
>> dependent on the package manager rather than displaying a warning that a
>> feature is missing is the brain dead way that plagues upgrades for
>> redhat and debian.  Of course if your intent is to make FreeBSD into
>> another Linux distro just with a different kernel, continue.
>>
>>     
>
> What is the problem of upgrading the package manager first and then
> upgrade the rest of the world without any problem?
>
>   
Not disagreeing with you... but making dependencies like this leads to
everything relying on the package manager being a particular version..
which in my opinion is wrong... the package manager is not part of the
software you're installing... and shouldn't be part of a dependency tree
- particularly when building your own ports.

*Every* time a Redhat and Debian system screwed up that I have had, was
caused by the package manager needing to be updated before a particular
package, then all the other dependent packages needed to be upgraded,
and the libraries and you end up with the catch 22 of the package
manager can't be installed because the package manager is too old and
you end up with a half working system that needs to be re-installed
because you needed to apply a security fix to a perl module....!  Now
FreeBSD has one advantage (currently) ... the package manager is not
part of the OS, it in itself is a port.. however that has half changed
already and in what, another month? it's going to be part of the OS...
Yeah sure keep building pkg-static so it can be installed independently,
but be aware that one does not want to get into dependency loops or
having to upgrade everything just for one security fix - particularly
when working with the ports tree and not the package manager... some
people have production servers that need a security fix, not an upgrade
of everything.

-- 
Michelle Sullivan
http://www.mhix.org/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542140E4.6050605>