[ENBD] Bring enbd back in Debian?

[Bas van Schaik]

Hi,

>>
>>>...
>>
>>Fine by me.  I can handle the upstream fixes and bug reports and make
>>the debian-specific parts as smooth as possible for you.
>> 
>>
> 
> Thanks for the support. I'll first think about the exact package
> structure, my first thoughts: enbd-server, enbd-client (depends
> on/suggests modules), enbd-client-modules. Any feedback is very welcome.

I decided to continue using this stucture:
enbd-client: contains client binaries and manpages
enbd-client-modules: contains client modules
enbd-server: contains server binaries and manpages

I'm not very sure about the enbd-client-modules package, I'll check the
opinion of a few Debian developers about how to package this according
to the Debian standards.

Splitting enbd into client and server packages is not very easy, though.
Currently, I'm having problems with the configfile /etc/enbd.conf and
it's manpage. Both packages are related to this configfile and the
manpage, but the files can't be in two packages at the same time. The
most ideal solution would be two different configfiles:
/etc/enbd/clients.conf and
/etc/enbd/servers.conf

or

/etc/enbd-clients.conf and
/etc/enbd-servers.conf

with two different manpages. I think this is a rather good idea, since
the syntax for client and server directives differs on many points.

Also the init.d script /etc/init.d/enbd can't be in two packages at the
same time. To be honest, I don't think may people will run client &
server on the same machine, because it doesn't make any sense to use a
networked block device when you can easily use a local one. So two
scripts /etc/init.d/enbd-clients and /etc/init.d/enbd-servers seems to
be the best solution.
Please let me hear your thoughts on this, because it affects not only
the Debian-package, but also the source package.

Regards,

--Bas