On Tue, Mar 19, 2019 at 10:05 PM Lucio <lucio.d...@gmail.com> wrote:
>
> I'm hoping this already has an answer, rather than require additional
> features. I also don't expect this to be a popular request, but I do consider
> its merits as greater than the disadvantages, so here goes.
>
> Efforts to eliminate the use of the Unix "make" command by producing a vastly
> more modern "go" command have been valiant and largely successful, in my
> opinion, at least, but I personally come up short on a regular basis, perhaps
> because I don't really know the "go" command as intimately as I ought to.
>
> As soon as I need a slightly unusual target in a development environment, I
> am prone to add an entry in a Makefile (actually "mkfile" as most of my
> development occurs in a Plan 9 environment), but I come against a barrier: I
> need to determine not only if local modules are more recent than the target,
> but also if related modules in imported packages are fresher than the target.
>
> I don't mind having to list the packages involved, ideally by the label I use
> within the code for each of them, that is acceptable. What I don't know how
> to do and suspect may need a small enhancement to the "go" command, is to
> reach into each package (directory) and verify that it is or is not reason to
> rebuild the target.
>
> What I just realised is that my Makefile/mkfile-foo isn't sufficient to *do
> something* with such information, but at this point I'm willing to cross that
> bridge when I come to it. For now, having a "go status infernal/package",
> say, even if it provides a single reply: "updated=yes", for example (someone
> here will think of a better approach, no doubt) will be a useful start.
> Obviously, the command is run in a directory other than the one being
> verified.
>
> Suggestions, from anyone, on how to do something like that? I don't mind
> getting my fingers dirty, but I'm hoping for the direction that makes such a
> facility as useful to as many Gophers as possible.
At first glance "go status internal/package" sounds like
test $(go list -f '{{.Stale}}' internal/package$) = "true"
If that doesn't work, can you explain what additional functionality
you're looking for?
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
