[Pkg-swan-devel] strongswan package split?
corsac at debian.org
Sat Nov 9 12:40:06 UTC 2013
I'm currently wondering about the various strongswan packages and the
way the binaries are split among them.
Right now, it seems that strongswan-ike (the main strongswan package,
shipping the charon daemon) also ship some useless stuff in most setups.
I wonder if we should reorganize the packages with something like
- a package with the charon daemon
- a package with some libs
- a package with basic plugins
- a package with extra plugins
with the minimal package with the charon daemon having just enough to be
able to setup a client or server in the most common cases (which I guess
are x509/pubkey setups).
I know the various file moves are painful, but I'm not really satisfied
with the current state of the packages.
What do you think?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: This is a digitally signed message part
More information about the Pkg-swan-devel