Re: [Cron-bug] Re: Cron stuff

[Jeff Bailey]

On Sun, Oct 21, 2001 at 11:48:58AM -0400, Ryan M. Golbeck wrote:

> > Do you want to have those is seperate directories off of the root?
> 
> Maybe in separate directories off of src/.  But I don't see each of
> the commands being too much code so it might not make sense to create
> a separate directory for each.  What do you think?  

Well, I have to confess that I tend to like writing one function per
file, and I also tend to use functions to organize my thoughts.  So a
simple program like at could have a dozen .[ch] files.

Also, I imagine that we'll have a 'libcron' directory for common functions.

> On related thought, do you have access directly to the CVS repository?
> That way if we say, stick them in just src/ and they seem to be
> growing too much we might just move them at the root to retain
> history?  Man, does CVS ever suck for this sort of thing. :)

Yeah, I do. =) The problem with moving things in the repository, is
that you lose the ability to get history by date accurately (the files
will be alwyas in their new location)

> Thinking ahead as well, when we eventually work on a translator for
> GNU cron, do you think that that should be under a separate module
> with it's own build environment, or another directory under src/?

I think just another directory.  It'll be told to only build when the
--build system is set to "gnu*"

> >> I suppose we should populate / with all the necessary stuff as
> >> well.  Have you ever used autoproject?  It adds some crap in
> >> there too that I haven't really liked, but it sets up a default
> >> build pretty fast.

> > I've never used it - It doesn't take me much more than 2 minutes
> > to setup autoconf/automake/libtool/gettext.

> > However you want to handle it, though.

> Probably much better if you do it by hand instead.

'k.

-- 
Abandon the search for truth; settle for a good fantasy.