From: Dario Faggioli <dario.faggioli@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] Add a "make rpmball" target
Date: Mon, 3 Mar 2014 18:27:03 +0100 [thread overview]
Message-ID: <1393867623.4058.144.camel@Solace> (raw)
In-Reply-To: <20140303172336.GA26596@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]
On lun, 2014-03-03 at 18:23 +0100, Olaf Hering wrote:
> On Mon, Mar 03, George Dunlap wrote:
>
> > >In this case, to avoid package conflicts, add some tags like:
> > >Obsoletes: xen-libs
> > >Obsoletes: xen-tools
> > What exactly would this be for?
>
> In my case it would replace the distro xen,xen-libs,xen-tools.rpm with
> the new xen.rpm. If none of these packages are installed, its a nop.
>
+1
In principle, I'd agree with George on the fact that is should well be
the developer to take care of this.
However, having the system thinking that, e.g., xen-libs is installed,
would allow one to install xen related libvirt distro packages, and test
them with the latest Xen, which would be pretty cool!
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-03 17:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:59 [PATCH] Add a "make rpmball" target George Dunlap
2014-03-03 16:07 ` George Dunlap
2014-03-03 22:34 ` Don Slutz
2014-03-03 23:08 ` Don Slutz
2014-03-03 23:37 ` M A Young
2014-03-03 23:46 ` Don Slutz
2014-03-03 23:52 ` M A Young
2014-03-04 10:26 ` George Dunlap
2014-03-03 16:23 ` Olaf Hering
2014-03-03 16:34 ` George Dunlap
2014-03-03 16:36 ` George Dunlap
2014-03-03 17:31 ` Olaf Hering
2014-03-03 17:23 ` Olaf Hering
2014-03-03 17:27 ` Dario Faggioli [this message]
2014-03-03 17:30 ` George Dunlap
2014-03-03 17:59 ` Ian Jackson
2014-03-03 22:53 ` Dario Faggioli
2014-03-03 23:11 ` Olaf Hering
2014-03-04 12:19 ` Ian Jackson
2014-03-03 18:19 ` Ian Campbell
2014-03-03 23:06 ` Olaf Hering
2014-03-03 20:51 ` Don Slutz
2014-03-04 11:41 ` George Dunlap
2014-03-03 22:52 ` Dario Faggioli
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=1393867623.4058.144.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/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.