Hello!

I am happy to announce the development of a Samba service for Guix.

Currently I am attending a technical college for informatics where I am
working on my final thesis that is due to be completed by February
next year.

Hence I have already proposed to develop and document the process
extending Guix.  So far I have managed to write a service that can
control nmbd, smbd and winbindd with default configuration options
provided by [1].  I have attached said service.  It is not intended for
production use yet, and needs to be extended to make more use of Samba's
capabilities.

The daemon samba itself has not been touched yet since it expects to
be a DC. It would need extra services too, especially kerberos, and
extensive scripting to run.  Printing has not been looked at either.
Documentation for info is missing.  I am not sure if the configuration
system I butchered from other service definitions is worthwhile or
could be done in an entirely different way.  Samba's configuration
system is extensive and flexible.  There are some extra package
definitions I want to write too.

I have not decided yet how far to go or how much of Samba should be
implemented as a service.  To implement the complete Samba suite would
exceed the scope of my assignment and will need proper testing until
it can be provided in Guix.  Hence I would like to implement sections
of it in such a way that can easily be extended at a later point,
should there be a need for it.

It is a little over a year already since I have installed my first
Guix system.  So far I have only been randomly handing in patches
every now and then with various success for new package definitions
while trying to learn more Scheme.  Preparing this service has
been a lot more educational than writing packages so far.

Kind regards,
Simon

[1] https://git.samba.org/samba.git/?p=samba.git;a=blob_plain;f=examples/smb.conf.default;hb=HEAD