Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
New version, after some rewrite and input by semarie Changes to PkgInfo. - fix a regexp bug... tests showed the issue. - simplify the -z option code, as it can actually share most of the code from the rest. This means pkg_info -zm for installed packages, and funnily enough, pkg_info -zm

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Here's another approach. I believe I do not need more than @option is-branch to actually mark branched ports... The current tree is clean enough that the last component of the pkgpath is always enough to disambiguate the path (even though there are some surprising choices of names). Follows a

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Scratch that, doesn't work for packages where the stem changes, e.g., GCC subpackages. Guess it will really need some kind of branch annotation... :(

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Here is what it turns out as, -z option to pkg_info Prints just simple stem--flavor[%branch] list of installed packages... Only manual installs, no need to encumber it with dependencies. Index: OpenBSD/PkgInfo.pm === RCS file:

next step, auto-branch determination

2016-06-25 Thread Marc Espie
The following very simple code shows that it's possible to figure out most of the branches (new % format) automatically based on comparison between fullpkgname and fullpkgpath. There are a few "false positive" (innocuous). I'm going to check soon that I have them all. This ought to yield a