>> Please commit so other people can start testing it.
>
> It does not even build because of libpromises mentioned by Stuart.
I must have done something wrong since the submitted version is running
on my machine for the last 24 hours without problems. Anyway, sorry for
submitting something that doesn't even build, my bad.
> * we do not want configuration files in /etc/cfengine like NetBSD,
> and Linux distros do?
>
> I am for symlink.
As stated in my mail, bootstrapping didn't work with the symlinked inputs
directory. This could be an issue with my policy or a general issue. In
the end I would rather stick to what cfengine.com is doing than to adopt
something because Linux and NetBSD are doing it that way. Mark Burgess,
the author of Cfengine, is a very smart guy and designed it this way with
good reasons...
> I wanted to submit RFE upstream not to override ppkeys symlink,
> as I've thought it could be symlinked to /etc/cfengine too, as
> it is "configuration".
I don't mind having the ppkeys in /var/cfengine, but I also don't mind
having them in /etc/cfengine either as long as it doesn't create more
porting work.
> * This is stupid output one gets with pkg_delete -c cfengine right
> after installation and running cf-key.
>
> See partial-cfengine... LOL. I really don't know how to solve
> this.
Before I saw Stuart's mail I was working on @exec-add the directories and
than @sample the configuration files to prevent these errors. But since
Stuart is way more knowledgeable in this area, I went with his setup.
Besides the @exec-add option we could also opt for something like the
following in the README and don't install anything in /var/cfengine.
Getting started
===============
During installation sample configuration files are placed in
${LOCALBASE}share/examples/cfengine/CoreBase/. Before you can use
Cfengine you need to create a public and private key pair by executing
cf-key as root. You should also copy the sample configuration files to
/var/cfengine/inputs/ and edit them to suit your needs.
When the user runs cf-key the needed directories will be created by
cf-key with the right permissions.
Kind regards,
Martijn Rijkeboer
