Re: [Cron-bug] Re: Cron stuff

[Ryan M. Golbeck]

Jeff Bailey <address@hidden> writes:

> On Sun, Oct 21, 2001 at 11:39:15AM -0400, Ryan M. Golbeck wrote:
>
>> > Nice - I'd like to setup some proper makefile, and I'd like to get the
>> > shell of the program sitting in src/ - It's *way* easier to just do
>> > the build environment right from the beginning.
>> 
>> Shell build environment, or setup as many skeleton source files as we
>> can as well?
>
> I think a skeleton programs that at least handles "--help" and
> "--version" command line options for crontab, crond, and at.
>
> 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?  

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. :)

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 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.

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

-- 
Ryan Golbeck <address@hidden>
Computer Science
University Of Waterloo

GPG: 1024D/78916B84 
1B1B 2A87 3F00 A7FB 40F3  526D 36CF BA44 7891 6B84