On Jul 27, 2016, at 6:37 PM, Robin Sommer
On the other hand, if, for example, somebody ends up
browsing the package source repository on GitHub, I'm sure they'd be
confused by all the packages pointing to very old versions.
Yeah, agree that is confusing and a problem of using submodules without ever updating them
in the source repo.
wondering if it would be worth switching to custom index instead of
submodules; seems that wouldn't be difficult either if indeed all we
need to do is track the external URLs somehow.
I’m on board with switching to a custom index format.
Also, if you want to
track discoverability metadata there already as well, seems that the
URL could just become part of that, no?
Any preference on the new index format? Single index file? Multiple files? INI, JSON,
I think still allowing package sources to be structured in a directory hierarchy is more
intuitive to navigate and maybe less intimidating to modify than a single file as the
source grows over time. And I’m already using INI format in 2 other places, so seems fine
to apply here, too. So a proposed structure of a package source:
url = https://github.com/alice/foo
keywords = Mr.T pity
url = https://github.com/alice/bar
keywords = club pub drinks
url = https://github.com/bob/baz
keywords = lightning storm
Output of `bro-pkg list all`:
- Would suggest to rename “pkg.meta” to, say,
- Does "upgrade" show the packages affected
and ask for confirmation?
I would suggest either doing that or require an --all option for
upgrading everything, as that's a potentially dangerous operation.
It doesn’t ask for confirmation, but in favor requiring the explicit --all.
- I suppose upgrading does (better: will do)
again, including making sure the Bro version matches the one that
update now requires?
Yes, I imagine the dependency analysis for upgrading and installing being the same or
- When installing the package manager as part of Bro,
could we pull in
the Python dependencies automatically, for example by installing
them into the same prefix?
Yes, I can likely get that to work.
Both GitHub and semantic_version are
pretty non-standard. Using them is ok I think but it would be nice
if "bro-pkg" wouldn't abort first thing because they aren't
Alternatively, I can have CMake detect whether they are installed, then, if not, don’t
install bro-pkg and put a warning/explanation in the CMake summary output. Let me know
which is preferred. I’m a bit in favor of auto-installing the python dependencies into
Bro’s install prefix.
- How about adding a note to either packages.bro or
packages/ directory that's it's automatically maintained and not
supposed to be manually messed with?
- In bro-pkg.conf, has "default" in
"[sources]" a special meaning, or
could it be any tag? Assuming the latter, I would just call it
It’s arbitrary, will change ‘default' to ‘bro’.
- For our default package source, do we want to
repositories? If so, a naming scheme by GitHub user won't work.
The hierarchy isn’t strictly required to use GitHub usernames. Generally could be
"$author_name/$package_name”, where the most common case is for $author to be a
GitHub user name. A domain name, company/organization name, or any string to help
identify the author would work.
- Suggest to rename
"../bro-package-manager" or "../bro-pkg”.
Agree about changing “package-manager” to “bro-package-manager”, but do you also mean to
get rid of the “lib” subdir? I think that fits within Filesystem Hierarchy Standard .
For /var/lib that says:
"State information. Persistent data modified by programs as they run, e.g.,
databases, packaging system metadata, etc.”
There’s probably nuances that let you get away with other locations when installing to
prefixes other than ‘/‘, but I find it generally works well to just replace ‘/‘ with
user’s preferred install prefix. Let me know what you think.
- Once we support dependencies on Bro versions, would
be nice if that
worked also with the "x.y-z" scheme that git master uses (and maybe
it just does anyways).
Should already work via semantic_version.
- Python 3.x works, right? Then I'd list that
Worked for me. Will do.
- A quick-start guide would be helpful that just
mentions the most
important steps, including basic installation along with Bro
itself (once that's merged).
Tried to do this in the Overview/README’s “Installation” section. I think reorganizing
that in smaller sections with bullet points to follow and re-labeling it as “quick-start
guide” may help.
- The "Installation" section becomes a
bit confusing towards with
the end with all those paths. Maybe split some parts out into an
advanced section or so?
Yeah, will try to re-organize.
- How-tos would be helpful that show by example how
to create a
(1) a pure script package, (2) and binary Bro plugin, and (3) a
Sure, I’ll add explicit step-by-step guides for each.