-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Bos wrote:
Op zaterdag 3 juni 2006 15:45, schreef Pascal Bleser:
The idea behind this is to be able to add a channel using the command: smart --install channel-<whatever name> It's even easier to provide .channel files somewhere (like the .repo files in the Build Service), and just do
smart channel --add http://......../guru.channel smart channel --add http://......../packman.channel
Not sure whether this is easier from a user perspective. In your case the user needs to remember the url pointing to the channel repository. In my proposal it is not needed to remember this. One could for example use smart's functionality to find the channel rpm. Once the correct rpm (providing the desired channel), just execute 'smart install channel-<name>'. Or the more lazy type of user could execute 'smart install '*<name>*.' and have the channel installed that way. The only requirement is to have all channel rpms in a common place. Just like the rpmkey rpms that I maintain at the moment.
That's correct, good point. I'd rather name them smart-channel-* though ;)
Your proposal just a *.channel repository is easier from a packager perspective, as there is not rpm needed. The advantage of having the channel files in an rpm, is that those gets updated automatically when the corresponding channel file gets updated. This is the same for the rpmkey rpms.
Yep, you're right.
The best place to host those channel rpms are of course suse itself as they get than mirrored automatically. But as you already stated that might not be possible due to law implications.
s/might/will/ I started a thread/discussion with the SUSE folks about that when openSUSE started. I was asking them whether it would be possible to do some refinements in YaST2, to have it fetch a list of repositories from, say, opensuse.org and propose them to the end-user as additional repos. It became pretty clear that it wouldn't be possible, because of ridiculous court rulings in the US and Germany (e.g. the Heise case), where "linking" to a resource that provides a package that under certain circumstances and/or jurisdictions would be.. well.. "attackable" in court, is already sufficient for potential trouble. The issue was a task to.. mm.. I think it was Adrian, to take it to Novell's legal dept, but there was never any feedback on it (and it was in November 2005). Dunno if anything came back about that.. Adrian ?
I think that the buildserver could build/create a channel rpm for each project and have those stored in a central place. This would be a good start.
It won't be in a central place, unfortunately. It could be done for repositories that don't contain stuff like mad or lame (which discards my repository and Packman, at the very least), like latest mozilla.org packages, latest wine packages by Marcus, latest OpenOffice.org packages, etc... But the other ones must be hosted elsewhere. Note that this structure would make it possible to host the/my smart RPMs in the openSUSE Build Service. I was very reluctant to the idea, and I'm still pretty sure it is going to make things more difficult for end-users but well... dunno... I'll think about it ;) The point is that to install e.g. smart-channel-packman, you'll have to add the Packman repository in the first place, because it won't be hosted in the Build Service... chicken vs egg. cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEgg6Nr3NMWliFcXcRAoIOAJ4yZ9WwZeETZ7PI3fHXxeIyf6NwawCdHHXE eGOJ5MWTdQloP47EMOYOpiQ= =n6iJ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org