Re: [Bro-Dev] bro-pkg -> bropkg
> On Sep 22, 2016, at 10:45 AM, Seth Hall wrote: > > 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 people have it installed. Quick follow up. I'm fine leaving things as-is. It's certainly easier and we can move on. :) .Seth -- Seth Hall International Computer Science Institute (Bro) because everyone has a network http://www.bro.org/ ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
> 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 people have it installed. .Seth -- Seth Hall International Computer Science Institute (Bro) because everyone has a network http://www.bro.org/ ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
Let's hold off if we might be renaming Bro On Sep 16, 2016, at 4:17 PM, Matthias Vallentin wrote: >> Bropkg is easier to type indeed. And then let's change the brocut. > > Yeah, all bro* utils should be consistent. If we change bro-pkg, then > bro-cut must undergo the same changes. > > Personally, I never had trouble typing "bro-pkg" though. Can we do a > Twitter poll to figure out what our users prefer? > >Matthias > ___ > bro-dev mailing list > bro-dev@bro.org > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
> I like Jon's idea to create a symlink for bro-pkg. One could also > install links for brocut and bro-ctl. PREFIX/bin/bro PREFIX/bin/bro-ctl PREFIX/bin/broctl PREFIX/bin/bro-cut PREFIX/bin/brocut PREFIX/bin/bro-pkg PREFIX/bin/bropkg .. That looks too confusing to me! My vote is to go with one scheme, ideally the one that breaks less existing tooling. Matthias ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
> No strong preference either way on my end, but let's not touch bro-cut > please, that's used in too many scripts. I like Jon's idea to create a symlink for bro-pkg. One could also install links for brocut and bro-ctl. ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
> Bropkg is easier to type indeed. And then let's change the brocut. Yeah, all bro* utils should be consistent. If we change bro-pkg, then bro-cut must undergo the same changes. Personally, I never had trouble typing "bro-pkg" though. Can we do a Twitter poll to figure out what our users prefer? Matthias ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
On Thu, Sep 15, 2016 at 19:25 -0500, you wrote: > Bropkg is easier to type indeed. And then let's change the brocut. No strong preference either way on my end, but let's not touch bro-cut please, that's used in too many scripts. Robin -- Robin Sommer * ICSI/LBNL * ro...@icir.org * www.icir.org/robin ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
Bropkg is easier to type indeed. And then let's change the brocut. > On 15 Sep 2016, at 13:53, Siwek, Jon wrote: > > Either way seems fine to me also. Maybe do a strawpoll and go w/ the > majority. Other misc. thoughts: > > Internally, I already used “bropkg” instead of “bro-pkg” for the name of the > Python package/API because Python discourages use of hyphens in > module/package names. But using the Python API isn’t a common use case and > figure most devs can handle doing “import bropkg” even though the > command-line tool is named “bro-pkg”. > > I don’t think there’s an argument to change it for the sake of aligning the > naming convention with “broctl” because there’s already "bro-cut”. The > hyphenation between those tools is already inconsistent or at least unclear > why one deserves hyphenation and the other doesn’t. > > If easier typing is the rationale, users do already have the option of > creating their own shell alias. > > Another idea is to keep the command line tool named “bro-pkg”, but also > install a symlink to it named “bropkg” for convenience. > > - Jon > >> On Sep 15, 2016, at 9:35 AM, Slagell, Adam J wrote: >> >> Someone did come up to me and ask about that during BroCon. >> >> I am indifferent, just please let’s not open up the whole tool name naming >> conversation. I don’t think I can take that again. :-) >> >>> On Sep 15, 2016, at 9:27 AM, Seth Hall wrote: >>> >>> What does everyone think about making a change to rename bro-pkg to bropkg? >>> I think we're early enough that we could probably get away with it and it >>> fits with more with existing tools like broctl. I find it difficult to >>> type the hyphen too for some reason. >>> >>> Thoughts? >>> >>> .Seth >>> >>> -- >>> Seth Hall >>> International Computer Science Institute >>> (Bro) because everyone has a network >>> http://www.bro.org/ >>> >>> >>> ___ >>> bro-dev mailing list >>> bro-dev@bro.org >>> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev >> >> -- >> >> Adam J. Slagell >> Chief Information Security Officer >> Director, Cybersecurity Division >> National Center for Supercomputing Applications >> University of Illinois at Urbana-Champaign >> www.slagell.info >> >> "Under the Illinois Freedom of Information Act (FOIA), any written >> communication to or from University employees regarding University business >> is a public record and may be subject to public disclosure." >> >> >> >> >> >> >> >> >> >> ___ >> bro-dev mailing list >> bro-dev@bro.org >> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev > > > ___ > bro-dev mailing list > bro-dev@bro.org > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
Either way seems fine to me also. Maybe do a strawpoll and go w/ the majority. Other misc. thoughts: Internally, I already used “bropkg” instead of “bro-pkg” for the name of the Python package/API because Python discourages use of hyphens in module/package names. But using the Python API isn’t a common use case and figure most devs can handle doing “import bropkg” even though the command-line tool is named “bro-pkg”. I don’t think there’s an argument to change it for the sake of aligning the naming convention with “broctl” because there’s already "bro-cut”. The hyphenation between those tools is already inconsistent or at least unclear why one deserves hyphenation and the other doesn’t. If easier typing is the rationale, users do already have the option of creating their own shell alias. Another idea is to keep the command line tool named “bro-pkg”, but also install a symlink to it named “bropkg” for convenience. - Jon > On Sep 15, 2016, at 9:35 AM, Slagell, Adam J wrote: > > Someone did come up to me and ask about that during BroCon. > > I am indifferent, just please let’s not open up the whole tool name naming > conversation. I don’t think I can take that again. :-) > >> On Sep 15, 2016, at 9:27 AM, Seth Hall wrote: >> >> What does everyone think about making a change to rename bro-pkg to bropkg? >> I think we're early enough that we could probably get away with it and it >> fits with more with existing tools like broctl. I find it difficult to type >> the hyphen too for some reason. >> >> Thoughts? >> >> .Seth >> >> -- >> Seth Hall >> International Computer Science Institute >> (Bro) because everyone has a network >> http://www.bro.org/ >> >> >> ___ >> bro-dev mailing list >> bro-dev@bro.org >> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev > > -- > > Adam J. Slagell > Chief Information Security Officer > Director, Cybersecurity Division > National Center for Supercomputing Applications > University of Illinois at Urbana-Champaign > www.slagell.info > > "Under the Illinois Freedom of Information Act (FOIA), any written > communication to or from University employees regarding University business > is a public record and may be subject to public disclosure." > > > > > > > > > > ___ > bro-dev mailing list > bro-dev@bro.org > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
Re: [Bro-Dev] bro-pkg -> bropkg
Someone did come up to me and ask about that during BroCon. I am indifferent, just please let’s not open up the whole tool name naming conversation. I don’t think I can take that again. :-) > On Sep 15, 2016, at 9:27 AM, Seth Hall wrote: > > What does everyone think about making a change to rename bro-pkg to bropkg? > I think we're early enough that we could probably get away with it and it > fits with more with existing tools like broctl. I find it difficult to type > the hyphen too for some reason. > > Thoughts? > > .Seth > > -- > Seth Hall > International Computer Science Institute > (Bro) because everyone has a network > http://www.bro.org/ > > > ___ > bro-dev mailing list > bro-dev@bro.org > http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev -- Adam J. Slagell Chief Information Security Officer Director, Cybersecurity Division National Center for Supercomputing Applications University of Illinois at Urbana-Champaign www.slagell.info "Under the Illinois Freedom of Information Act (FOIA), any written communication to or from University employees regarding University business is a public record and may be subject to public disclosure." ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
[Bro-Dev] bro-pkg -> bropkg
What does everyone think about making a change to rename bro-pkg to bropkg? I think we're early enough that we could probably get away with it and it fits with more with existing tools like broctl. I find it difficult to type the hyphen too for some reason. Thoughts? .Seth -- Seth Hall International Computer Science Institute (Bro) because everyone has a network http://www.bro.org/ ___ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
