Excerpts from Dan Callaghan's message of 2013-02-21 16:26:22 +1000: > So anyway, I think the answer here is to drop the mention of it from > the *harness* API, since we aren't expecting the harness to rely on > this variable. Whether the environment variable happens to be set > system-wide by Beaker for *tasks* is a separate question.
On second though, no I think this is a bad idea. We need to make it clear who is setting what environment variables for whom. That is, Beaker should be setting environment variables for the harness (*not* for tasks), and the harness should be responsible for setting whatever is needed in the task environment. If we let some task env vars be system-wide ones from Beaker and others have to be set by the harness, things will get messy. (Of course, the current reality is already messy in this regard, but at least we should be converging towards cleanliness...) So, I will add the variable back. BEAKER_HUB_URL seems good enough. I don't think it makes sense to call it a "hub", we inherited that word from Brew/Koji (through Kobo) but there's already precedent in Beaker for it so I'm fine with it. -- Dan Callaghan <dcall...@redhat.com> Software Engineer, Infrastructure Engineering and Development Red Hat, Inc.
signature.asc
Description: PGP signature
_______________________________________________ Beaker-devel mailing list Beaker-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/beaker-devel
