[bind10-dev] Running individual applications from the source tree

[Jelte Jansen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/27/2010 05:55 AM, zhanglikun wrote:
>>
>> There is a ticket that Jeremy is working on right now, #158:
>>
>> https://bind10.isc.org/ticket/158
>>
>> There was a problem with the magic script we use to run the boss from
>> the source tree itself, now fixed.
>>
>> My question is, do we need to be able to run other applications directly
>> from the source tree (like xfrin in this case)? I have never done so,
>> but I can see how it might be useful for development or testing.
>>
>> My goal here is not to waste time doing work that we don't find useful.
>> Do people think we should maintain this capability? If so, I'll ask
>> Jeremy to continue with this ticket. Otherwise, we can remove the
>> various run_foo.sh scripts.
> 
> Just append some jabber chat on this topic to promote more ideas
> 
> 15:06:04jreed:  Is it really important to run all of bind10 from source
> tree? Adding special cases for socket files, zone databases, spec files, etc
> seems like overkill to do something that would not be done in real life.

not necessarily in source tree, but it is quite common to be able to
specify specific locations for for instance files that are used, like
internal sockets and pid files (for one example within this project,
being able to override the socket file for msgq would allow one to run
multiple bind10 instances).

I think (though i'm not sure) the common trick though is to make the
source tree have the same layout as the installed one, but I certainly
don't want to go there (i think the layout is quite nice now).

If we provide flexibility in the environment I think the first target is
to run from the source tree, which I personally use all the time (both
here and in other self-compiled stuff).

That being said, I do think we're doing it wrong. In at least two ways :)

Being able to run specific modules by hand is right now quite essential,
but I don't think we need a run_XXX.sh script for everything. I don't
even think we need one. If we provide a general sourceable script that
sets up the environment in your shell (yes, this would be
shell-specific), like the run scripts do now, we should be able to run
everything by hand.

The other thing is that we should probably get rid of the FROM_SOURCE
variable, and make feature-specific ones, if at all possible (these
could be for a set of features though). Yes, I am aware that I am the
one who added that ;)

Smaller fish may be that bob is trying to be a bit too smart right now,
and perhaps we need more command-line options to what it's running,
instead of doing half of it through environment and half through arguments.

A completely different option (or addition) would be a base .conf file ,
which everything needs to accept and contains all stuff like this, some
options just aren't dynamic.

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkv+KjUACgkQ4nZCKsdOncUnpACaAy6sD1dt04L3btD8GN2rd3gp
SCQAoL7KtrKzVFMa7aJMPIqEs0I3ZuDY
=GskU
-----END PGP SIGNATURE-----