28.06.2013 21:38, Mateusz Viste пишет: >> If VDE does not replace any of your code, then I immediately >> stop talking about it. :) (since anyway it doesn't seem to have >> any advantages on other fronts too) > Well, it does replace pretty much all of my code - since both > librouter and vdeslirp do the same thing. The main difference is that > they embed the slirp code from qemu, while I call the standalone slirp > app instead. > >> Maybe VDE can also be integrated? > I'm pretty sure it can. But I have no idea at what development cost :) Well, but you wanted to embed slirp anyway, and haven't started that yet. So maybe it would be the same cost to evaluate the embedding of slirp and the cost of embedding vde? :)
> Now that I think about it, I'm not sure anymore it's good to > artificially embed slirp.. apart being 'all in one binary', it doesn't > really provide any added value after all. > Adding slirp as a separate executable is probably wiser, then at least > curious users can understand how it works exactly, and the dosemu > binary is not bloated. > > For example having files like: > /usr/bin/dosemu.bin > /usr/bin/dosemu.slirp We can also package slirp separately and ask the user to install an extra package if he needs slirp. dosemu.slirp is not extremely good, as there can then appear also qemu.slirp, vbox.slirp etc. AFAIK some distros (like fedora) already adopted the rule to not allow any duplications like that. They likely won't even allow to embed slirp - their policies are very strict. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
