Hi folks With the lack of responses to my restructuring the last weeks, it looks like pkg-xen is dead. Now, what to do? My favorite is to merge it into the kernel repository where I have my infrastructure (archive and autobuilders for snapshots for example) to properly work on it. Bastian -- No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060830/7ef8d797/attachment.pgp
On Wed, Aug 30, 2006 at 05:38:40PM +0200, Bastian Blank wrote: Hi! ;)> With the lack of responses to my restructuring the last weeks, it looks > like pkg-xen is dead. > > Now, what to do? My favorite is to merge it into the kernel repository > where I have my infrastructure (archive and autobuilders for snapshots > for example) to properly work on it. >As I told you on irc your restructuring started when I was away on vacation and was pretty massive, so I still haven't had time to look at it! I'm still interested to work on xen and I think we should at least check what other people here want to do, maybe a bit later after summer has ended! ;) Anyway for me it's not a big issue to have it here or in another svn repository, except of course that since it's already here we might want to think if there's really a reason to move it... The infrastructure for autobuilding the kernel and xen is different anyway, isn't it? So wouldn't it be the same if we autobuilt this repo? ;) Guido
On Wed, Aug 30, 2006 at 05:38:40PM +0200, Bastian Blank wrote:> With the lack of responses to my restructuring the last weeks, it looks > like pkg-xen is dead. > > Now, what to do? My favorite is to merge it into the kernel repository > where I have my infrastructure (archive and autobuilders for snapshots > for example) to properly work on it.I thought this had already been discussed at length and it was decided that Xen (minus kernel patch) should live in its own project? As I understand it there are several other active maintainers working on Xen in pkg-xen (at least Guido Trotter and Julien Danjou) - would moving it make it harder for them to work on it? Logically speaking I can't see that Xen belongs in the kernel repository; most of the packaging challenges are not directly related to the kernel itself but the userspace tools. I've not personally managed to have any time to work on the Xen packages yet but I'm likely to be able to in the future, and needing to be in the kernel team would probably make things harder. Do other kernel team members have any opinions on wanting Xen in the kernel project? Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
I've been out of the loop for awhile as I recently moved cross-country and started a new job so I've had limited time and resources at the moment. I do not thing that the team is dead as it was discussed in quite length previously that Xen should be kept separate from the kernel. I still believe this is true now and will continue to be so until such time that Xen code becomes part of the main upstream kernel releases. Before that happens I'm sure we'll see the Xen source code split so that tools/application code is separate from the kernel code at which point the tools/apps can be maintained by the team and the kernel team can maintain the kernel portions. Regards, Jeremy On 8/30/06, Bastian Blank <waldi@debian.org> wrote:> > Hi folks > > With the lack of responses to my restructuring the last weeks, it looks > like pkg-xen is dead. > > Now, what to do? My favorite is to merge it into the kernel repository > where I have my infrastructure (archive and autobuilders for snapshots > for example) to properly work on it. > > Bastian > > -- > No one wants war. > -- Kirk, "Errand of Mercy", stardate 3201.7 > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > > iEYEARECAAYFAkT1sP8ACgkQnw66O/MvCNGGvQCfQJUDRkW2aPEH4lYHZ5vHsWOP > Le8AoKgj/jbdosvegduDb+K5Ku3GPAI5 > =TrLB > -----END PGP SIGNATURE----- > > > _______________________________________________ > Pkg-xen-devel mailing list > Pkg-xen-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-xen-devel > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20060831/fc37c4f1/attachment.htm
Reasonably Related Threads
- [PATCH] Use pkg-config (if available) to detect libogg. Fall back to old method if pkg-config fails.
- [PATCH] Use pkg-config (if available) to detect libogg. Fall back to old method if pkg-config fails.
- how to exclude a pkg in yum .conf
- cvs commit: ports/multimedia/win32-codecs Makefile distinfo pkg-plist
- Running example in pkg-Ex.R failed