Hi,

On Sat, 2016-03-26 at 21:18 +0100, Jonatan Schlag wrote:
> Hi,
> I have 3 questions which concern Libvirt.
> 1. 
> When have I to build something (like cmake) and I do not need it in the core
> or as a package because I only need it to build an another package, where
> should I put the rootfiles ? All lines are excluded so when I put it into
> config/rootfiles/packages the build process fails because tar tries to pack
> nothing which is impossible. Should I put them into in config/rootfiles/common
> like cmake? I need your advice :-).

Put them into common and comment all the lines so no files are included in the
image.

> 2. 
> Libvirt needs to communicate over a normal SSH session, a Netcat
> implementation which can communicate with Unix Sockets. This implementation
> has to be the standard Netcat, which is provided over usr/bin/nc. There are
> two implementations which can communicate with Unix Sockets: Netcat-openbsd (
> the most distribution ship this implementation as standard netcat) and Ncat
> since version 7.0  the implementation of the Nmap Project (Fedora and RHEL
> (CentOS)) ship this implementation as the standard Netcat. 
> IPFire ship in the moment the GNU Netcat as standard Netcat. This conflicts
> with libvirt because the GNU Netcat cannot communicate with UNIX Sockets. To
> solve this I would suggest to
> 	1. Ship GNU Netcat no longer as standard Netcat
> 	2. Ship Ncat as Standard Netcat (It is easier because OpenBSD requires
> on library to build, Ncat build already on IPFire)
> 	3. Provide Ncat as a single package because I do not want Nmap, nping
> and all other things which pending to Nmap if I only need Ncat. 
> What do you think about that? This is no decision which I could make alone.

I think you should replace nc by the version that is in RHEL/Fedora then.

> 3.  
> How could I split up the content of one source package in two different IPFire
> packages? In the moment, I build Nmap the first time and  install every thing
> into the build directory and then  I install manually the Ncat binary. After
> that, I build Nmap without Ncat. Is this the only way do provide Ncat
> Standalone?

This is probably quite difficult. I would prefer a lfs/nmap and a seperate
lfs/netcat. That will generate a single rootfile for each of them and you can
decide what to do with each of them.

Hope this answers the questions. If not, please mail back.

> 
> Regards Jonatan

-Michael