Marc Espie a écrit :
>On Mon, Jul 30, 2012 at 08:43:39AM +0200, Antoine Jacoutot wrote:
>> So, after a quick chat with Marc Espie trying to understand why a
>> particular package would not run @exec-add, I would like to warn you
>> guys when you use such a marker in your ports.
>> In my case, @
On Mon, Jul 30, 2012 at 11:59:10AM +0200, Marc Espie wrote:
> On Mon, Jul 30, 2012 at 11:33:55AM +0200, Antoine Jacoutot wrote:
> > On Mon, Jul 30, 2012 at 11:06:30AM +0200, Marc Espie wrote:
> > > No, this is definitely not a feature.
> (by which I mean it's a bug)
> > >
> > > Those are rather ob
On Mon, Jul 30, 2012 at 11:33:55AM +0200, Antoine Jacoutot wrote:
> On Mon, Jul 30, 2012 at 11:06:30AM +0200, Marc Espie wrote:
> > No, this is definitely not a feature.
(by which I mean it's a bug)
> >
> > Those are rather obvious cases where pkg_add is confused.
(by which I say pkg_add is buggy)
On Mon, Jul 30, 2012 at 11:06:30AM +0200, Marc Espie wrote:
> On Mon, Jul 30, 2012 at 08:43:39AM +0200, Antoine Jacoutot wrote:
> > So, after a quick chat with Marc Espie trying to understand why a
> > particular package would not run @exec-add, I would like to warn you
> > guys when you use such a
On Mon, Jul 30, 2012 at 08:43:39AM +0200, Antoine Jacoutot wrote:
> So, after a quick chat with Marc Espie trying to understand why a
> particular package would not run @exec-add, I would like to warn you
> guys when you use such a marker in your ports.
> In my case, @exec-add was not run because I
So, after a quick chat with Marc Espie trying to understand why a
particular package would not run @exec-add, I would like to warn you
guys when you use such a marker in your ports.
In my case, @exec-add was not run because I had some .libs-foo still
installed on the system which where @conflicting
