On Thu, Sep 29, 2016 at 20:49 +, you wrote:
> ‘bundle’ and ‘unbundle’ commands are now available in bro-pkg 0.7 and
> should work as described earlier in the thread.
Great, many thanks! I'll give it a try soon.
Robin
--
Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin
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
After discussion with some more folks, and the email thread, some
further tweaks to my original "bundle" proposal:
- Following Justin's suggestion, unbundling should by default not
replace everything currently installed; and instead offer a
"--replace" option if one wants that.
> On Sep 21, 2016, at 9:54 AM, Robin Sommer wrote:
>
> What are the default paths? In other words, where do the downloaded
> packages get put if I don't set anything further up?
They get put within ~/.bro-pkg/
(The Advanced Configuration [1] section has more usage info related
On Tue, Sep 20, 2016 at 04:11 +, you wrote:
> Sounds great.. What you are describing is basically source and binary
> packages.
Not sure "binary package" is the right term, at least for the first
part of your description (where nothing gets built). The difference
seems more to be having
> On Sep 19, 2016, at 11:11 PM, Azoff, Justin S wrote:
>
> Sounds great.. What you are describing is basically source and binary
> packages.
In concept, I like the idea of simply extending the “install” command to be
able to install from a source or binary packages, but
> On Sep 19, 2016, at 6:27 PM, Robin Sommer wrote:
>
> @Jon: Do you think this would be doable that way?
Yeah, looks viable.
> - I’m not quite sure if the bundle should contain just the packages
> themselves or further bro-pkg state as well, such as which packages
> are
Sounds great.. What you are describing is basically source and binary packages.
The only thing I would do differently is that you wouldn't want bundles (at
least not as the only feature) but individual source and binary packages.
For example
bro-pkg install sethhall/domain-tld
would still
At BroCon several people pointed out a need to install Bro packages on
machines that do not have a direct external connection. One idea would
be some kind of proxy scheme where an intermediary git repository
mirrors packages locally; bro-pkg would then pull from there. However,
I don't think any