rice 2.0: move away from source parsing and use a Ricefile? about go.rice HOT 7 OPEN

The current rice tool cannot use build tags, another reason to move away from source analysis and towards a configuration file for boxes.

from go.rice.

Appears the current rice tool fails when multiple packages live in the same directory too.

from go.rice.

multiple packages in the same directory? That should never happen right? (maybe exceptionally when one package has -buildflag and the other has +buildflag). @burdges

from go.rice.

Appears not. At least, it does not happen where I once thought I'd seen it happen, thanks!

from go.rice.

There's another reason to do this - FindBox calls in global scope will work until the user uses embed-go, at which point it will fail, since variables are initialized before the init() functions are called. This has already confused people, as in issue #67.

from go.rice.

I just needed to implement the ability for rice to append boxes without access to source files. Only just noticed this issue after I've finished, sorry about that. I've implemented slightly differently ..

If you're in a directory that has only the box contents but no source, you can run this:

rice appendbox --exec <executable> -b <box1> [ -b <box2> ]

See boyvinall@appendbox

from go.rice.

@boyvinall I also came across this issue after having problems with source parsing. I implemented it similarly on the command line here - JonathanTech#1 . I added it as a separate command instead.

rice append-simple -b <box1> [-b <box2>] --exec <executable>

from go.rice.