Its round 1 of our patchsets here in FreeBSD land. This more or less stubs out the code for FreeBSD support. We will flush out that code in following patchsets. _______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
According to Fedora guidelines, because we bundle gnulib we need to add a virtual Provides: bundled(gnulib). https://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries#Requirement_if_you_bundle --- netcf.spec.in | 2 ++ 1 file changed, 2 insertions(+) diff --git a/netcf.spec.in b/netcf.spec.in index cec69c1..234561b 100644 --- a/netcf.spec.in +++ b/netcf.spec.in @@ -14,6 +14,8 @@ BuildRequires: libxml2-devel libxslt-devel BuildRequires: libnl-devel Requires: %{name}-libs = %{version}-%{release} +Provides: bundled(gnulib) + %description Netcf is a library used to modify the network configuration of a system. Network configurations are expressed in a platform-independent -- -- 1.7.10.1 _______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
On 05/14/2012 12:38 PM, Sean Bruno wrote: > On Thu, 2012-05-10 at 17:53 -0700, Laine Stump wrote: >> On 05/10/2012 08:07 PM, Sean Bruno wrote: >>> So, Hiren and I are approaching our first milestone, where we think that >>> we're feature complete for freebsd. We're working out a few details at >>> the moment, but its starting to look good. >>> >>> In order for you guys to pull from us, what's the standard process for >>> us to follow such that you can review, accept(and/or reject) and pull >>> from our tree. >>> >>> I assume there's some kind of "generate review-able patches" guidelines >>> we should follow to make your lives easy. >> Pretty simple, really - just make sure your patches are on a local git >> branch that's based off the fedorahosted master branch, and use git >> send-email --compose -<# of patches>, giving the introductory message >> the subject [PATCH 0/<# of patches>] <something descriptive> and a short >> overview. >> >> A series of small patches is much better than a single monolithic patch. >> Especially - if you've done any refactoring of the existing code to make >> your code fit in better, it would be better to put that first in a >> separate patch (such that applying it would have 0 functional effect), >> then your port-specific stuff in later patches. >> >> ______________________________________ > Since my git-foo is pretty weak, I'm pretty conservative here. > > Should I branch another copy of the the project repo (yours) and apply > patches from our repo to the new copy and then send the patches from(Continue reading)
So, Hiren and I are approaching our first milestone, where we think that we're feature complete for freebsd. We're working out a few details at the moment, but its starting to look good. In order for you guys to pull from us, what's the standard process for us to follow such that you can review, accept(and/or reject) and pull from our tree. I assume there's some kind of "generate review-able patches" guidelines we should follow to make your lives easy. Sean _______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
Hi, Thanks Eric and Laine for your earlier comments. Here is a small set of 3 cleaner patches which are enough to make netcf build on debian. (patches on top of git head). I will try my hand at the autoconf magic needed for libnl support next. thanks, -serge _______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
Hi guys, following is the set of patches applied in the Ubuntu package. I was sure I had sent these before, but they're not in the archive. I was wondering why there had never been any discussion! Sorry about that. thanks, -serge _______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
On 10/28/2011 09:53 AM, Serge E. Hallyn wrote: > Quoting Daniel P. Berrange (berrange <at> redhat.com): >> On Thu, Oct 27, 2011 at 11:04:52PM -0500, Serge E. Hallyn wrote: >>> Quoting Serge E. Hallyn (serge.hallyn <at> canonical.com): >>>> Ah, an email from the good folks over at libguestfs suggested always doing >>>> an aug_save() after any aug_set(). Doing that fixed it for me. It seems >>>> more problematic since aborting partway through will result in a bad >>>> interfaces file, so I may have to add rollback after all, but right now I'm >>>> just glad it's working :) >>> And now I've figured out the root of the problem - me. I was forcing >>> get_augeas to rerun aug_load() every time. >> Cool, glad it know it now does in fact work for someone other than >> myself(Continue reading)>> >>> A tree which works for me on debian and ubuntu is at: >>> >>> http://bazaar.launchpad.net/~serge-hallyn/+junk/netcf/files >> Are you planning on submitting those patches to this list ? The libnl ones >> will probably need to have some kind of conditional compilation, so we can >> support both versions of libnl. > Yes, absolutely. I was thinking about trying to clean them up first, > but that probably means I'll never get to them so maybe I'll send them > today. Serge, After getting some netcf-related libvirt bug reports identified as coming from an ubuntu system, I realized that you must now have a released netcf build for ubuntu, but it's based on an upstream netcf git checkout rather than a release. Any chance you could post the patches
change-begin - mark the beginning of a set of revertible network config changes
change-commit - commit the pending network config changes
change-rollback - rollback (revert) a set of network config changes
Hi folks,
Can someone please take some time out to explain how these commands are supposed to work?
what is the input and output of these commands?
it seems we take snapshots of current configurations? can someone shed some light, please?
Thanks in advance,
Hiren
_______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
_______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
Just a note of introduction as Hiren has been nice enough to keep the questions to you guys coming when we are on the bus in the morning to the offices. He and I are thwacking on netcf at the moment in order to move on to libvirt and then on to virtualization support on FreeBSD. So, you fine folks are the first stop on this little journey that ends up with libvirt support for BHyVe ... at some point. Cheers. Sean
_______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
"define" takes an xmlfile as an argument, is that same as output of dumpxml?
And undefine would delete the interface from the configuration altogether.
Is my understanding correct?
Thanks a lot,
Hiren
_______________________________________________ netcf-devel mailing list netcf-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/netcf-devel
RSS Feed16 | |
|---|---|
12 | |
39 | |
12 | |
3 | |
5 | |
14 | |
41 | |
3 | |
23 | |
35 | |
1 | |
5 | |
2 | |
25 | |
2 | |
51 | |
5 | |
16 | |
10 | |
2 | |
5 | |
3 | |
5 | |
4 | |
16 | |
21 | |
74 | |
65 | |
26 | |
76 | |
107 | |
6 |
