On Wed 26 Oct 2011 21:34:52 NZDT +1300, Stefan Seyfried wrote:
Example: stuff in the (badly named) CrossToolchain:avr repo: IIRC it installs totally unacceptable (for general use) udev rules that allow all users in the "users" group access to all (usb?) serial ports.
Instead of raving over badly packaged software that enhances the usability of your distribution considerably (and openSUSE is still rather short on a lot of things that matter to professionals in their respective fields) you could provide more information to help remedy the situation. In http://en.opensuse.org/openSUSE:Packaging_guidelines e.g. the eclipse plugin heading is empty. Handling of udev rules and cross compilers isn't even mentioned. I have been trying to re-compile avr-gcc and it's been a bit of a process. Can you point me to something please that explains what configure options to use so that it goes under /usr instead of /opt without interfering with the system's gcc on openSUSE?
=> unacceptable for general usage (think of a worm sending expensive SMS via your mobile phone / 3G card)
The rules I see there identify various USB programmers by their IDs and set them mode 666 (I look forward to your project description of how to send SMS with AVR MCU programmers...). Parallel port anything however seems to be set to 666 too, so not so good. For reference, I have a professional SCSI film scanner that SUSE was never once able to handle in any usable way. Can you please point me to openSUSE's guidelines on how to create udev rules in packages for things like MCU programmers?
=> makes the AVR stuff "just work" for developers (which is important to them)
I expect many users of the avr packages are not developers in your sense of the word, but people who need to get their electronics equipment working without spending time on operating systems that is subtracted from time available for their projects. openSUSE could do more to support those users. The naming of pretty much anything in the build service is messy and very confusing. I'm having a hard time determining even what repos are vendor-supplied and which are user-supplied, which isn't too good. Colons add much to the confusion. Is all this repo-naming user generated, or does it need staff access rights (and therefore fixes)? The build service is brilliant but the repos are a mess. Thanks, Volker -- Volker Kuhlmann http://volker.dnsalias.net/ Please do not CC list postings to me. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org