> On Sep 21, 2016, at 5:03 PM, Fernandez, Mark I wrote:
>
> Design guidance: is it acceptable to redefine/extend the ‘conn_id’ record as
> described above?
You probably don't want to extend the conn_id record. There are some cases
where it can cause trouble doing lookups because the conn_id
> On Sep 16, 2016, at 4:57 PM, Robin Sommer wrote:
>
> No strong preference either way on my end, but let's not touch bro-cut
> please, that's used in too many scripts.
Yeah, I think changing bro-cut is too far gone at this point. I was only
asking about bro-pkg because it's so new and so few
Seth,
>> Is there somewhere else you could stash the information that you need?
Yes, I re-worked the script yesterday to redef/extend the HTTP::Info record and
store the information there. But I notice it works differently than before,
and I must do some extra effort to store it in the HTTP::I
> On Sep 21, 2016, at 2:45 PM, Robin Sommer wrote:
>
>- Following Justin's suggestion, unbundling should by default not
> replace everything currently installed; and instead offer a
> "--replace" option if one wants that.
What happens when --replace is not used and different versi
On Thu, Sep 22, 2016 at 15:39 +, you wrote:
> What happens when --replace is not used and different version of a
> package that’s in the bundle is already installed? I think asking
> user whether it’s ok is the way to go,
Agree, plus a "--force" option once more to skip any questions for
b