Re: [Cooker] Contrib package: zero-inst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Tholen wrote: On Thursday 05 June 2003 11:32, Buchan Milne wrote: (BTW, I require kernel-source for the win4lin kernel packages I am working on, so if we're going to consider win4lin-multimedia kernel images you need to provide kernel-source so other users don't need to - --nodeps on build ...) But if you run kernel-multimedia, you will need to build against kernel-multimedia-source. If i just require kernel-source there is a risk it builds against wrong kernel? But also the possibility that the user wants it this way. For win4lin it is a bit different (since patches are likely to differ between stock and multi-media), but win4lin SRPMS can have tighter requires then. For most kernel modules, there should be no need to change anything on the package to make it work on mm kernels vs stock kernels, so there is no reason to have mutliple SRPMS. win4lin-multimedia should just require kernel-source-multimedia? Or alternatively i can let the source conflict with normal kernel. wdyt? Once again, win4lin-multi-media is a bit different, from say ltmodem, NVIDIA etc kernel modules, which should be able to build against any kernel-source. I see kernel-multimedia does not provide kernel, is there any reason why I should not be able to have only a multimedia kernel? I'll have to consider some changes in some packages, which were using output of 'rpm -q kernel-source' for kernel revision, but ideally we should allow to compile kernel modules with multiple kernel-source packages installed, package version determined by where /usr/src/linux points to (version.sh in the Mandrake NVIDIA RPMs like the one I mailed on the club list should get this right AFAIK). Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+35OprJK6UGDSBKcRAh3GAKCqph9F2tB8mUfW7cXuD8x5nX/7VwCfcKgf OslBSa+cP1qtCk6U2x0QvSE= =d3SW -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
Re: [Cooker] Contrib package: zero-inst
On Thursday 05 June 2003 11:32, Buchan Milne wrote: (What if you're using kernel-multimedia? kernel-multimedia-source should provide kernel-source. Danny? In 9.1 it provides alsa-source and kernel-multimedia-source. (BTW, I require kernel-source for the win4lin kernel packages I am working on, so if we're going to consider win4lin-multimedia kernel images you need to provide kernel-source so other users don't need to - --nodeps on build ...) But if you run kernel-multimedia, you will need to build against kernel-multimedia-source. If i just require kernel-source there is a risk it builds against wrong kernel? win4lin-multimedia should just require kernel-source-multimedia? Or alternatively i can let the source conflict with normal kernel. wdyt? d.
Re: [Cooker] Contrib package: zero-inst
On Thursday 05 June 2003 21:02, you wrote: Once again, win4lin-multi-media is a bit different, from say ltmodem, NVIDIA etc kernel modules, which should be able to build against any kernel-source. I see kernel-multimedia does not provide kernel, is there any reason why I should not be able to have only a multimedia kernel? no, you can only have the multimedia kernel. But if you build against kernel-multimedia-source the modules will ofcourse not work on a normal kernel. d.
Re: [Cooker] Contrib package: zero-inst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Tholen wrote: On Thursday 05 June 2003 21:02, you wrote: no, you can only have the multimedia kernel. I think I would have to uninstall at least the following RPMs: [EMAIL PROTECTED] bgmilne]$ rpm -q --whatrequires kernel quota-3.08-1mdk pciutils-2.1.11-2mdk basesystem-9.2-1mdk nfs-utils-1.0.1-1mdk bootsplash-1.4.1-1mdk nfs-utils-clients-1.0.1-1mdk libalsa2-0.9.2-5mdk alsamixergui-0.9.0-0.7rc1_2mdk Unless kernel-multimedia provides kernel, which AFAIK it doesn't. My logic was that if kernel-multimedia provides kernel, then kernel-multimedia-source should provide kernel-source ... But if you build against kernel-multimedia-source the modules will ofcourse not work on a normal kernel. But at present, one has to --nodeps to build say an NVIDIA kernel-module RPM if the SRPM BuildRequires: kernel-source ... Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+4GucrJK6UGDSBKcRAkECAJ41bininNo48SiRsuEiLmW1wUmMVgCfZ+vO X5gzgoQB2PPHLHyEkZ5rbC0= =Kovi -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
Re: [Cooker] Contrib package: zero-inst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Tholen wrote: On Friday 06 June 2003 12:23, you wrote: Unless kernel-multimedia provides kernel, which AFAIK it doesn't. My logic was that if kernel-multimedia provides kernel, then kernel-multimedia-source should provide kernel-source ... it does provides kernel You sure? $ rpm -qp --provides /var/ftp/pub/mandrake/9.1/contrib/RPMS/kernel-multimedia-2.4.21.0.16mdk-1-1mdk.i586.rpm kernel-multimedia = 2.4.21 alsa module-info kernel-multimedia-2.4.21.0.16mdk = 1-1mdk $ rpm -qp --provides /var/ftp/pub/mandrake/contrib/RPMS/kernel-multimedia-2.4.21.0.18mdk-1-1mdk.i586.rpm kernel-multimedia = 2.4.21 alsa module-info kernel-multimedia-2.4.21.0.18mdk = 1-1mdk $ rpm -qp --provides /var/ftp/pub/mandrake/contrib/RPMS/kernel-multimedia-smp-2.4.21.0.18mdk-1-1mdk.i586.rpm kernel-multimedia = 2.4.21 alsa kernel-multimedia-smp-2.4.21.0.18mdk = 1-1mdk $ urpmq -p kernel kernel-2.4.21-0.rc1.1mdk|kernel-linus2.4|kernel-enterprise-2.4.21-0.rc1.1mdk|kernel-secure-2.4.21-0.rc1.1mdk|kernel-smp-2.4.21-0.rc1.1mdk Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+4HnTrJK6UGDSBKcRAl2mAJ9DnzZ4cjbfsRuXTwQwEAbldUJT4QCgmVgA 0pft+rQ2BxxKJMM0yzZlLCc= =wEmj -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
Re: [Cooker] Contrib package: zero-inst
On Friday 06 June 2003 12:23, you wrote: Unless kernel-multimedia provides kernel, which AFAIK it doesn't. My logic was that if kernel-multimedia provides kernel, then kernel-multimedia-source should provide kernel-source ... it does provides kernel But at present, one has to --nodeps to build say an NVIDIA kernel-module RPM if the SRPM BuildRequires: kernel-source ... hmm..well..it might be sensible to provide kernel-source. will do on next update. but I am a little bit afraid that people start building modules against the the normal kernel source instead of the mm kernel source. d.
Re: [Cooker] Contrib package: zero-inst
On Friday 06 June 2003 13:24, Buchan Milne wrote: You sure? no :) $ rpm -qp --provides /var/ftp/pub/mandrake/9.1/contrib/RPMS/kernel-multimedia-2.4.21.0.16mdk-1-1 mdk.i586.rpm kernel-multimedia = 2.4.21 alsa module-info kernel-multimedia-2.4.21.0.16mdk = 1-1mdk well, seems i was wrong. Stupid me. will fix as well. d.
Re: [Cooker] Contrib package: zero-inst
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andi Payn wrote: From the package description: The Zero Install System is a URI-based network filesystem, together with a mechanism for running applications (including any necessary libraries) directly off the internet. Instead of installing an application, a zero-inst user can just start the application by its URI. Any needed binaries are downloaded and cached locally, so there's essentially no speed hit. For frequently-used applications, a user can add a menu entry, web link, bash alias, etc. that points to the URI. Note that zero-inst is still a work in progress. Since it requires a kernel patch, and the whole point is to run binaries directly from the internet, it's probably a bad idea to use zero-inst on a production system at this stage. See http://zero-install.souceforge.net for more details. I get a 404 on this site. I have serious issues with this idea, unless it is coupled with the DRM kind of stuff Linus mentioned a while back, such as signed binaries and the kernel module requiring validation of all binaries before use. The zero-inst developers are all Rox users, so the documentation is a bit focused on Rox users, but it works just fine with any KDE, GNOME, or no desktop at all. However, at present, there are only a few demo programs available for zero-inst (all in /uri/http/zero-install.sourceforge.net/demo, and all built only for ix86), so it's not terribly useful yet. The source package builds two binary packages: zero-inst and zero-inst-kernelmod. You need to have the kernel source for the kernel you want to run against to build the package, and you need to be using the matching kernel version to install the -kernelmod package. I couldn't think of a good way to check this. I put in a BuildRequires: kernel-source but that doesn't really cover it. It should, mostly. (What if you're using kernel-multimedia? kernel-multimedia-source should provide kernel-source. Danny? In 9.1 it provides alsa-source and kernel-multimedia-source. (BTW, I require kernel-source for the win4lin kernel packages I am working on, so if we're going to consider win4lin-multimedia kernel images you need to provide kernel-source so other users don't need to - --nodeps on build ...) Or if you've upgraded to a new kernel but still have the old kernel-source?) No problem if you have the modules themselves, doesn't matter which source is installed (actually, it's probably best to upgrade kernel-source and build all kernel-dependant packages before rebooting into the new kernel. And there doesn't seem to be any way to make the binary package require the kernel version used for building (another feature for automated requirements gathering?). You have to do this yourself at present, it's not difficult. The kernel module handles the virtual filesystem; updating the cache is done with user-space tools. The tool to automatically download files the first time (zero-install) is pretty much complete, but the tools for throwing away old cached files when they're unneeded (or for updating to newer versions) aren't. Also, while zero-install is downloading files, the parent process locks up with no feedback, and the tools to see what's happening are only partially complete (try the 0show command-line tool). I slapped together an init script, RPM pre/post scripts, etc. in about a half hour, and they may need more work--it seems to work fine for me; that's all I can promise. I have some example spec files, (win4lin kernel images, NVidia kernel modules, ltmodem kernel modules) if you want to see how it's done. Regards, Buchan - -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x202 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+3w4rrJK6UGDSBKcRAsz2AJ9nafgDLxqiWWYPH/YOZzWRi8cRZwCfSbcV rMh7TaNTCQtQhBNIZpDxcVk= =b2E7 -END PGP SIGNATURE- ** Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. **
[Cooker] Contrib package: zero-inst
From the package description: The Zero Install System is a URI-based network filesystem, together with a mechanism for running applications (including any necessary libraries) directly off the internet. Instead of installing an application, a zero-inst user can just start the application by its URI. Any needed binaries are downloaded and cached locally, so there's essentially no speed hit. For frequently-used applications, a user can add a menu entry, web link, bash alias, etc. that points to the URI. Note that zero-inst is still a work in progress. Since it requires a kernel patch, and the whole point is to run binaries directly from the internet, it's probably a bad idea to use zero-inst on a production system at this stage. See http://zero-install.souceforge.net for more details. The zero-inst developers are all Rox users, so the documentation is a bit focused on Rox users, but it works just fine with any KDE, GNOME, or no desktop at all. However, at present, there are only a few demo programs available for zero-inst (all in /uri/http/zero-install.sourceforge.net/demo, and all built only for ix86), so it's not terribly useful yet. The source package builds two binary packages: zero-inst and zero-inst-kernelmod. You need to have the kernel source for the kernel you want to run against to build the package, and you need to be using the matching kernel version to install the -kernelmod package. I couldn't think of a good way to check this. I put in a BuildRequires: kernel-source but that doesn't really cover it. (What if you're using kernel-multimedia? Or if you've upgraded to a new kernel but still have the old kernel-source?) And there doesn't seem to be any way to make the binary package require the kernel version used for building (another feature for automated requirements gathering?). The kernel module handles the virtual filesystem; updating the cache is done with user-space tools. The tool to automatically download files the first time (zero-install) is pretty much complete, but the tools for throwing away old cached files when they're unneeded (or for updating to newer versions) aren't. Also, while zero-install is downloading files, the parent process locks up with no feedback, and the tools to see what's happening are only partially complete (try the 0show command-line tool). I slapped together an init script, RPM pre/post scripts, etc. in about a half hour, and they may need more work--it seems to work fine for me; that's all I can promise.
