On Sun, May 20, 2012 at 12:13 PM, Florian Schlichting <fschl...@zedat.fu-berlin.de> wrote: > [...] > a) src:vpnc builds a new package vpnc-script(s) containing the script in > its current location with legacy patches, perhaps including a few more > commits which I expect upstrem to commit to SVN until the end of May; > after wheezy, we move on to unpatched vpnc-scripts.git
When you say move to vpnc-scripts.git, do you mean a separate src:vpnc-scripts package? > b) you go ahead packaging the git scripts and using them from openvpn, > and I move vpnc over to depending on that package when I'm ready. If your answer to the above was "yes", then these both end up at the same long-term conclusion, correct? It's just a difference in how we get there. > [...] > I'm somewhat AFK for the next seven days; I'd say feel free to choose > either path or something else, but let's not stir up the current vpnc > package too much at this time. Yes, I completely understand that you have a working package and configuration and that it's probably more work for you to migrate to a different setup than for me to add a new feature. If you agree that the best long-term solution is a separate src:vpnc-scripts package, then I will start working on that. Thanks for your feedback. -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
