Forcing pkg

[Mark Martinec]

2014-09-04 02:00 Michael Ross wrote:
> On Thu, 04 Sep 2014 01:34:21 +0200, Paul Koch <paul.koch at akips.com> 
> wrote:
> 
>> On Thu, 04 Sep 2014 00:27:16 +0200
>> "Michael Ross" <gmx at ross.cx> wrote:
>> 
>>> Hello,
>>> 
>>> a second pkg question:
>>> 
>>> Assume I have to install something *now*, like in: 5 minutes ago,
>>> production on fire,
>>> never mind corrupt pkg databases or anything, sort out later, need  
>>> service
>>> up:
>>> 
>>> Is there any equivalent to "pkg_add --force"?
>>> 
>>> As in, *I* know the dependencies are met, and I *know* that pkg is 
>>> wrong
>>> in complaining?
>>> 
>>> -DDISABLE_CONFLICTS doesn't work anymore?
>> 
>> Or, I want to install pkg A, but it relies on pkgs B, C, D,...
>> I only want to use a single program in pkg A that I "know" has
>> no dependencies and really don't want to pull in anything else.
>> 
> 
> like what would have been
> 
>      -i, --no-deps
>              Install the package without fetching and installing  
> dependencies.
> 
> to pkg_add.
> 
> Michael


Another example over which I'm currently stuck:

   # pkg install mailman  (or, same with: pkg upgrade)
   The following 3 packages will be affected (of 0 checked):

   Installed packages to be REMOVED:
         postfix-current-2.12.20140709_2,4

   New packages to be INSTALLED:
         postfix: 2.11.1_4,1

   Installed packages to be UPGRADED:
         mailman: 2.1.18.1_1 -> 2.1.18.1_3

I don't want the postfix-current to be removed. Mailman is perfectly
capable of working with it and does not need postfix: 2.11.1.


Even if I follow this path: remove postfix-current, install mailman
and let it install postfix: 2.11.1, then try to remove postfix: 2.11.1
and install postfix-current - it tries to deinstall mailman.

   Mark