From: Jim Fehlig <jfehlig@novell.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Is Xend versioned?
Date: Tue, 08 Jan 2008 19:06:04 -0700 [thread overview]
Message-ID: <47842C0C.7070709@novell.com> (raw)
In-Reply-To: <200801041808.20614.mark.williamson@cl.cam.ac.uk>
Mark Williamson wrote:
>> When querying Xend for version this code is invoked in
>> tools/python/xen/xend/XendNode.py
>>
>> def xen_version(self):
>> info = self.xc.xeninfo()
>>
>> try:
>> from xen import VERSION
>> info = {'Xen': '%(xen_major)d.%(xen_minor)d' % info,
>> 'Xend': VERSION}
>> except (ImportError, AttributeError):
>> info = {'Xen': '%(xen_major)d.%(xen_minor)d' % info,
>> 'Xend': '3.0.3'}
>>
>> I cannot find a xen module from which to import VERSION, resulting in
>> the hardcoded one. I would cook up a patch if I understood how, or even
>> if, it should be versioned.
>>
>
> You're right, I can't see what this is supposed to achieve...
>
> If you were to add:
>
> VERSION = "blah"
>
> to tools/python/xen/__init__.py
>
> then I imagine that would do the right thing. As for whether it's necessary,
> I'm not sure... But presumably that code ought either to do something or to
> be removed???
>
I'm not sure there is any value in versioning xend itself. Certainly
its interfaces (e.g. XenAPI) should be versioned but the whole daemon?
I will spin a patch to remove it (or fix it) if there is consensus.
Regards,
Jim
prev parent reply other threads:[~2008-01-09 2:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 19:08 Is Xend versioned? Jim Fehlig
2008-01-04 18:08 ` Mark Williamson
2008-01-09 2:06 ` Jim Fehlig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47842C0C.7070709@novell.com \
--to=jfehlig@novell.com \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.