Am Sunday 04 June 2006 12:54 schrieb Pascal Bleser: > Adrian Schröter wrote: > > Am Sunday 04 June 2006 00:34 schrieb Pascal Bleser: > >> Richard Bos wrote: > > ... > > >>> 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 ? > > > > The problem is that this decisions needs to be made for each software > > seperatly. For example it is very unlikely that this would be ever > > possible with DeCSS, but there are maybe chances for other stuff like mp3 > > playback. This will of course take much resources for each package at the > > legal department :/ > > OK, now I get it, I thought it was some blessing of linking to > repositories that provide packages that ... > > Note, I'm not talking about building and hosting packages like mad in > the Build Service, that's another topic.
Yes, I understood that, but there seems no to be much difference between linking and building it legal wise. -- Adrian Schroeter SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
