On Thu, Dec 14, 2006 at 11:21:50AM +0100, Piotr Roszatycki wrote: > Hi. I've found that you uploaded new vde2 package. I didn't find the source > for the package, so I'd like to ask:
Hi. Renzo Davoli, the main VDE author, asked Guido and me to create a new package for VDE2. There was no recent activity on the vde package so we went on with the packaging. I'm sure we should and can join our efforts for a better vde2 package :-) so I'll try to answer all your questions. First of all, we keep the source code for VDE on SourceForge (project name VDE) and it's updated to the latest version (currently 2.1.5 which I released a few days ago). The Debian-related files are hosted on alioth under the "pkg-vsquare" project. It includes Debian files for other software written by Renzo, me and others. All this software is linked to virtual machines and networks (see http://www.virtualsquare.org) and our intention is to create Debian packages for other projects as well. We have no problems in leaving the maintenance of VDE packages to you and, if needed, in adding you to the members of pkg-vsquare. And now, your questions. > * Does the vde2 package interfere with vde package? As for now, yes. Binaries have the same names and places in vde and vde2; in fact we added a Conflict in vde2 against vde. We don't see this as a problem, because vde2 has complete backwards compatibility with vde and it't much more reliable and bug-free. 1.x series of VDE should not be used anymore. > * Does it contain some additional patches? Being the authors of VDE we decided to put everything in the main CVS tree: we see no point in having debian-specific patches. > * Does it provide /etc/network/interfaces support? No. I took a quick look to your support and it seems complete and useful. I think it should be included in the official vde2 package. > * Does it support non-root users? I'm not sure I've fully understood this question. Strictly speaking, vde2 never needs root access. The only case it may be needed is when you want to connect a vde_switch to a tap interface (I agree that's often the case, but not always) and nobody created a persistent tap interfaces for you. But also in this case you can create a persistent tap interface with tunctl with the correct owner and let a non-root user start the vde_switch. > * Is it uploaded to experimental or sid? I think it's uploaded to Sid, but Guido is the Debian expert of this group. :-) I don't know if this is the best solution for release times, but I want to stress the fact that vde2 is *much* more stable than vde. Lots of bugs have been fixed in the vde2 branch and not in vde 1.x. > * Your package is splitted on 3 different binary packages. Why? I think the > vde2 package should provide all files. We did this splitting for a good reason, or at least we think so. :-) Let me try to explain: - libvdeplug is a library that everyone can use to write his own vde-compatible application (e.g. qemu or vdetelweb - that's a web interface to vde that hasn't been packaged yet). This wants to be a quite stable package with a well defined API and we don't want a program to depend on the whole VDE package just for a little library that allows it to connect to a switch (maybe on a different host) - vde_cryptcab has been splitted from the main package because of specific requests from many users. The main point is "we don't want to be forced to install OpenSSL libraries if we don't need the SSL part of VDE." vde_cryptcab (sort of a vde_plug over an encrypted UDP channel) is the only tool that depends on SSL and it's not vital to VDE. > * New vde2 package doesn't provide upgrade path for users of old vde package. I suppose the only upgrade that may be needed is in your /etc/network/interfaces part (but I'm not sure -- I haven't checked it very well). vde2 aims to substitute vde in a quite painless way. The control socket (i.e. /var/run/vde.ctl) now is a directory containing various sockets, but usually nobody notices this in the everyday use, unless one tries to connect a vde_plug from vde 1.x to a vde_switch from vde2. In that case he must specify the socket name /var/run/vde.ctl/ctl instead of the dir name, but that's all. > I would like to offer my help and patches. My vde2 package is available at > http://people.debian.org/~dexter/vde2 > The SVN source is available at > svn://svn.debian.org/cvsdebuild/trunk/debian/dists/vde2 We'll take a look and, if you have no objections, we could try to merge your additions to the main tree. Do you have specific advices or anything? > Please reconsider the package splitting. Please let the ftp-master know, that > he should remove currently uploaded vde2 package from NEW queue. Please, > review my patches and /etc/network scritps. I explained you the reasons that pushed us towards the splitting and, if you find them reasonable, we'd like to keep them in this way. Of course we're open to suggestions. We'll notify the ftp-master. Thank for your work. Sadly, we worked on the same thing for some time and we didn't know of each other. If you need to contact us, please write again to our 4 addresses (you mistyped Guido's address, now I put his official Debian one) or to [EMAIL PROTECTED] In this way we will all read your mail and our reply will be faster (the vde2 package really needs to be released... :-)). Ludovico -- <[EMAIL PROTECTED]> #acheronte (irc.freenode.net) ICQ: 64483080 GPG ID: 07F89BB8 Jabber: [EMAIL PROTECTED] Yahoo: gardenghelle -- This is signature nr. 2772 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
