make. I'm trying to
make this a generic solution that doesn't require a user or
administrator to delve into the policy manual, and that still
completely works within the package system.
Interesting idea though with fetching/storing configuration files via a
revision control system. I think it woul
On Sat May 16, 2009 at 04:20:20PM +0100, Colin Tuckley wrote:
> Mark Lawrence wrote:
>
> >To include everything in your home directory you add
> >a line containing ’*’. However, be aware that
> >building a package requires t
responsible for the decryption of
files. It can be used in the event that things do not
succeed during installation (wrong password, unattended
install, etc).
SEE ALSO
debuild(1), ccrypt(1)
AUTHOR
Mark Lawrence
COPYRIGHT AND LICENSE
Copyright (C) 2009 Mark
3 matches
Mail list logo
