Re: [Cron-bug] Build environment

[Ryan M. Golbeck]

Jeff Bailey <address@hidden> writes:

> I have checked in the build environment as we discussed on IRC.  I
> have also made a small patch to your cron-specs.texi so that it names
> the file correctly.

What is src/cronttab for?

>
> Lastly, I have started the ChangeLog and think that we should keep
>it up to date.  I generally like an entry in the ChangeLog for just
>about everything, but your call.
>

Agreed.  Wasn't sure if there should be a separate one in doc/ or not
though.  Since noting changes to documentation isn't as useful to
users.


We should probably start with deciding what needs to go in libcron to
make sure we don't code redundant functions into each of the commands.

So, basically we follow the GNU library standard for coding it?
Exported functions are one per file, with static functions in that
file if need be.  And we have have the private functions in other
files?  Tell me more about your one function per file deal. :)

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

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