Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Phil Dibowitz wrote: Douglas E. Warner wrote: Okay, thanks for the examples. AFAICT, the rules.d folder is just so packages can ship their own scripts, not to enable/disable them through some other mechanism. If you don't mind, I'd prefer that we just stick the udev rule in /etc/udev/rules.d and forget about the symlink. If you'd like to keep it this way I can easily fix it in Fedora land in the package, no problem. I don't feel strongly, so I changed your patch to modify this as well. It now does it this way. Either way, let me know when the patch is merged and I'll try to build a new libconcord package to make sure everything is working as-intended. Submitted. Looks good; packages built without any patching this morning straight from CVS. -Doug signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
On Wed, Mar 04, 2009 at 08:25:09AM -0500, Douglas E. Warner wrote: Phil Dibowitz wrote: Douglas E. Warner wrote: Okay, thanks for the examples. AFAICT, the rules.d folder is just so packages can ship their own scripts, not to enable/disable them through some other mechanism. If you don't mind, I'd prefer that we just stick the udev rule in /etc/udev/rules.d and forget about the symlink. If you'd like to keep it this way I can easily fix it in Fedora land in the package, no problem. I don't feel strongly, so I changed your patch to modify this as well. It now does it this way. Either way, let me know when the patch is merged and I'll try to build a new libconcord package to make sure everything is working as-intended. Submitted. Looks good; packages built without any patching this morning straight from CVS. Great! That's exactly what I wanted to here. Thanks. OK, when I get some time this week I'll do the release. I have a checklist somewhere I'll be submitting to CVS as well, but off-hand it's something like - update so-version of lib - make sure py/perl/etc. libs that need an updated version get that - update concordance version - update the Changelog to note new version and date - make distclean rebuild test - do an export, initialize the autoconf/automake stuff tar release - update supported models page -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: Digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Sorry; I was trying to make some modifications to the install path + use $(DESTDIR) and get that patch together; Doh! I knew I was forgetting something. I'll check in a fix now. Sorry. Well, actually the patch I'm working on also tries to not regenerate the files during the install phase, but my auto-foo is currently lacking. I'll get a patch of the patch changes put together tomorrow, and we can work out the re-generation issue later if necessary. Yeah, my auto-foo sucks as well. I'm pretty sure there's a better way to do what I did, but it's good enough for now. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Phil Dibowitz wrote: Phil Dibowitz wrote: Douglas E. Warner wrote: Sorry; I was trying to make some modifications to the install path + use $(DESTDIR) and get that patch together; Doh! I knew I was forgetting something. I'll check in a fix now. Sorry. [p...@rider libconcord]$ DESTDIR=/tmp/test make install_policykit ./gen_udev_support -p Creating udev file: libconcord.rules ... done Creating hal policy file: libconcord.fdi ... done Creating PolicyKit file: org.freedesktop.hal.device-access.libconcord.policy ... done /bin/mkdir -p /tmp/test/etc/udev/rules.d /bin/sh /home/phil/build/cvs/concordance/libconcord/install-sh -c -m 644 libconcord.rules /tmp/test/etc/udev/ (cd /tmp/test/etc/udev/rules.d ln -f -s ../libconcord.rules 99_libconcord.rules) /bin/mkdir -p /tmp/test//usr/share/hal/fdi/policy/10osvendor/ /bin/mkdir -p /tmp/test//usr/share/PolicyKit/policy/ /bin/sh /home/phil/build/cvs/concordance/libconcord/install-sh -c -m 644 libconcord.fdi \ /tmp/test//usr/share/hal/fdi/policy/10osvendor/99-libconcord.fdi /bin/sh /home/phil/build/cvs/concordance/libconcord/install-sh -c -m 644 org.freedesktop.hal.device-access.libconcord.policy \ /tmp/test//usr/share/PolicyKit/policy/ [p...@rider libconcord]$ Cool; I'll check that out this morning and modify the install path for the policy file and we should be set. I'll send you a patch shortly. -Doug signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Phil Dibowitz wrote: Phil Dibowitz wrote: Douglas E. Warner wrote: Sorry; I was trying to make some modifications to the install path + use $(DESTDIR) and get that patch together; Doh! I knew I was forgetting something. I'll check in a fix now. Sorry. Cool; I'll check that out this morning and modify the install path for the policy file and we should be set. I'll send you a patch shortly. Question: why symlink the udev rule from /etc/udev to /etc/udev/rules.d? The systems I've looked at (Fedora, Debian) just install the file to /etc/udev/rules.d; it's probably best not to pollute /etc/udev. -Doug signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Phil Dibowitz wrote: Phil Dibowitz wrote: Douglas E. Warner wrote: Sorry; I was trying to make some modifications to the install path + use $(DESTDIR) and get that patch together; Doh! I knew I was forgetting something. I'll check in a fix now. Sorry. [p...@rider libconcord]$ DESTDIR=/tmp/test make install_policykit Cool; I'll check that out this morning and modify the install path for the policy file and we should be set. I'll send you a patch shortly. Here we go; it uses $(sysconfdir) instead of hard-coding /etc/ and fixes a typo in the consolekit installation. This doesn't fix the /etc/udev / /etc/udev/rules.d question I had, but that's fairly minor. -Doug Index: Makefile.am === RCS file: /cvsroot/concordance/concordance/libconcord/Makefile.am,v retrieving revision 1.8 diff -u -r1.8 Makefile.am --- Makefile.am 3 Mar 2009 08:19:58 - 1.8 +++ Makefile.am 3 Mar 2009 14:33:56 - @@ -12,16 +12,16 @@ ./gen_udev_support -u install_udev_generic: - $(MKDIR_P) $(DESTDIR)/etc/udev/rules.d - $(install_sh_DATA) libconcord.rules $(DESTDIR)/etc/udev/ - (cd $(DESTDIR)/etc/udev/rules.d ln -f -s ../libconcord.rules 99_libconcord.rules) + $(MKDIR_P) $(DESTDIR)$(sysconfdir)/udev/rules.d + $(install_sh_DATA) libconcord.rules $(DESTDIR)$(sysconfdir)/udev/ + (cd $(DESTDIR)$(sysconfdir)/udev/rules.d ln -f -s ../libconcord.rules 99_libconcord.rules) install_udev: udev install_udev_generic policykit: ./gen_udev_support -p -install_policykit: policykit install_udev_generic +install_policykit: policykit install_udev_generic $(MKDIR_P) $(DESTDIR)$(datarootdir)/hal/fdi/policy/10osvendor/ $(MKDIR_P) $(DESTDIR)$(datarootdir)/PolicyKit/policy/ $(install_sh_DATA) libconcord.fdi \ @@ -35,4 +35,5 @@ install_consolekit: consolekit install_udev_generic $(MKDIR_P) $(DESTDIR)$(datarootdir)/hal/fdi/policy/10osvendor/ $(install_sh_DATA) libconcord.perms \ - $(DATDIR)$(datarootdir)/hal/fdi/policy/10osvendor/99-libconcord.perms + $(DESTDIR)$(datarootdir)/hal/fdi/policy/10osvendor/99-libconcord.perms + signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
On Tue, Mar 03, 2009 at 09:59:17AM -0500, Douglas E. Warner wrote: Douglas E. Warner wrote: Phil Dibowitz wrote: Phil Dibowitz wrote: Douglas E. Warner wrote: Sorry; I was trying to make some modifications to the install path + use $(DESTDIR) and get that patch together; Doh! I knew I was forgetting something. I'll check in a fix now. Sorry. Cool; I'll check that out this morning and modify the install path for the policy file and we should be set. I'll send you a patch shortly. Question: why symlink the udev rule from /etc/udev to /etc/udev/rules.d? The systems I've looked at (Fedora, Debian) just install the file to /etc/udev/rules.d; it's probably best not to pollute /etc/udev. lrwxrwxrwx 1 root root19 2007-07-21 23:57 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root22 2009-01-30 22:19 025_logitechmouse.rules - ../logitechmouse.rules As an example. My understanding is it was supposed to be like that - an init.d type system. As it turns out, only a few are like that, not most... so I don't really care. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: Digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Okay, thanks for the examples. AFAICT, the rules.d folder is just so packages can ship their own scripts, not to enable/disable them through some other mechanism. If you don't mind, I'd prefer that we just stick the udev rule in /etc/udev/rules.d and forget about the symlink. If you'd like to keep it this way I can easily fix it in Fedora land in the package, no problem. I don't feel strongly, so I changed your patch to modify this as well. It now does it this way. Either way, let me know when the patch is merged and I'll try to build a new libconcord package to make sure everything is working as-intended. Submitted. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Phil Dibowitz wrote: On Thu, Feb 26, 2009 at 06:58:49PM +0100, Phil Dibowitz wrote: On Wed, Feb 18, 2009 at 10:38:48AM -0500, Douglas E. Warner wrote: Here we go; attached gen_udev_support script. OK, changes I've made to your patch: - Files that are *linked* to (policykit, for example) the files are *not* named 99- they are named just libconcord... or whatever since the Makefile targets than link to them appropriately. I actually made all of them not have 99-*. I don't think th escript should choose their install place. Either the Makefile or perhaps the specfile/debconf/etc. should do that. And in fact, the Makefile.am committed does that. I wasn't clear on where the policykit file goes. I'm nearly certain I have it going to the wrong place. Doug, can you test the checked in code? You should want make policykit and make install_policykit I actually checked that in from a plane. Yay for internet access on planes! Anyway, I'm back in town now - I'd just like confirmation on this before I get ready to roll the next release... -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
On Thu, Feb 26, 2009 at 06:58:49PM +0100, Phil Dibowitz wrote: On Wed, Feb 18, 2009 at 10:38:48AM -0500, Douglas E. Warner wrote: Here we go; attached gen_udev_support script. OK, changes I've made to your patch: - Files that are *linked* to (policykit, for example) the files are *not* named 99- they are named just libconcord... or whatever since the Makefile targets than link to them appropriately. I actually made all of them not have 99-*. I don't think th escript should choose their install place. Either the Makefile or perhaps the specfile/debconf/etc. should do that. And in fact, the Makefile.am committed does that. I wasn't clear on where the policykit file goes. I'm nearly certain I have it going to the wrong place. Doug, can you test the checked in code? You should want make policykit and make install_policykit Thanks! -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: Digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Phil Dibowitz wrote: On Wed, Feb 18, 2009 at 10:38:48AM -0500, Douglas E. Warner wrote: Here we go; attached gen_udev_support script. You broke things a bit for the non-policykit non-consolekit folks. I'll apply this and send a fixed version out. It sounds like you're OK with the general structure of the script as well as th eMake targets I threw in? Does it satisfy all of your requirements? I'd like this release to not require packagers to have to add scripts/files/etc. to make the package work as intended for users. Ah, sorry about that. I didn't realize the udev scripts were different from the one I was editing and the one you had. Yeah, I'm definitely okay with moving the targets into the Makefile so I don't have to install things in a custom fashion. I briefly looked over the Makefile patch and it looked good to me. The only thing we might want to look into in the future is to modify the configure script to choose the correct version of the udev helpers automatically. -Doug signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Sorry this is taking me so long to get worked out; it looks like the PolicyKit rules I previously wrote don't work anymore (at least on my box). The udev rules are working fine, but I just can't get access to the device from a regular user. I'll try to figure out what's going on today. Okay, I think I have an updated gen_udev_support script that generates: * udev rules (alias /dev/harmony* to the correct usb device) * ConsoleKit perms (pre-PolicyKit that used pam_console to grant access to devices) * PolicyKit perms (includes a hal script to assign the correct keys to the hal device as well as the PolicyKit policy) Fedora only currently supports PolicyKit (ConsoleKit was dropped in F9) but since we had the rules I kept them in the script but just cleaned up the names of variables. I'm packaging up things now to test and will post the updated script once I know that's good. -Doug signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Douglas E. Warner wrote: Douglas E. Warner wrote: Sorry this is taking me so long to get worked out; it looks like the PolicyKit rules I previously wrote don't work anymore (at least on my box). The udev rules are working fine, but I just can't get access to the device from a regular user. I'll try to figure out what's going on today. Okay, I think I have an updated gen_udev_support script that generates: * udev rules (alias /dev/harmony* to the correct usb device) * ConsoleKit perms (pre-PolicyKit that used pam_console to grant access to devices) * PolicyKit perms (includes a hal script to assign the correct keys to the hal device as well as the PolicyKit policy) Fedora only currently supports PolicyKit (ConsoleKit was dropped in F9) but since we had the rules I kept them in the script but just cleaned up the names of variables. I'm packaging up things now to test and will post the updated script once I know that's good. -Doug If you need an example of where these files go, see [1]. 99-libconcord.rules - /etc/udev/rules.d/ 99-libconcord.fdi - /usr/share/hal/fdi/policy/10osvendor/ org.freedesktop.hal.device-access.libconcord.policy - /usr/share/PolicyKit/policy/ -Doug [1] https://rpm.silfreed.net:8002/file/c40b8b21e228/libconcord/libconcord.spec signature.asc Description: OpenPGP digital signature -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
Phil Dibowitz wrote: Thoughts? Comments? Sorry, I didn't comment earlier, I didn't read it thoroughly enough to realize that you hadn't committed this yet and started building test packages ;) The script in general looks good; I need to do some testing on my current udev/policykit rules to make sure they're working properly and/or installed properly. Something's not right (but I haven't received any bug reports either, hmm) since I've been needing to run it w/ sudo whereas I didn't previously. My only question would be which part of the package do you think you would put the udev/policykit stuff in? I had been building them as part of the concordance binary since it was necessary to use it as a normal user, but now that I think about a little more it may make more sense to have them be part of libconcord so other front-ends like congruity can be used w/o sudo as well. -Doug signature.asc Description: OpenPGP digital signature -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Getting udev/policykit/etc. in place for 0.21
On Thu, Feb 12, 2009 at 09:01:36AM -0500, Douglas E. Warner wrote: The script in general looks good; I need to do some testing on my current udev/policykit rules to make sure they're working properly and/or installed properly. Something's not right (but I haven't received any bug reports either, hmm) since I've been needing to run it w/ sudo whereas I didn't previously. OK, give it a shot and let me know what you find. My only question would be which part of the package do you think you would put the udev/policykit stuff in? I had been building them as part of the concordance binary since it was necessary to use it as a normal user, but now that I think about a little more it may make more sense to have them be part of libconcord so other front-ends like congruity can be used w/o sudo as well. Definitely in the libconcord directory. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible -- Taylor's Laws of Programming signature.asc Description: Digital signature -- Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
[concordance-devel] Getting udev/policykit/etc. in place for 0.21
Hey all (especially packagers):
I want to make sure we have usable udev and policykit support in 0.21. I
have scripts that are roughly similar to the ones Doug posted here:
https://rpm.silfreed.net:8002/file/9181b7d0c023/harmony/
But there's a couple situations I want to support, and more importantly, I
want things to work well for packagers. Here are the various things I'm
thinking about, and I'd like input:
1. Not all distros use policykit, and whether or not you're using
policykit changes your udev rules. This instantly creates the need to
be able to generate two kinds of udev files.
2. It's gotta (assuming the user knows if they use policykit) gotta just
work with a run this script as root to setup udev with the right
argument (more on this later).
3. If at all possible I'd like it to be something packagers use so they
don't have to keep their udev and/or policykit scripts in sync.
So I'm wrote a script that works like this:
gen_udev_support [-u|-p]
Where -u (udev-only) generates rules like:
SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=0660,
GROUP=dialout
But -p (policykit) generates rules like this:
ATTR{idVendor}==046d, ATTR{idProduct}==c111, SYMLINK+=harmony-%k'
And then a corresponding policykit rule file to match it and a policykit
permissions rules ala:
harmony=/dev/harmony*
console 0600 harmony 0600 root
(The policykit stuff is completely ripped from Doug's fedora package.)
It generates these in the local directory, and it would get run by an
appropriate make target such as make udevonly or make udev_policykit
and then a make install_$whatever would install them in the right place.
The sample script I wrote is:
http://www.phildev.net/concordance/gen_udev_support
It doesn't have a good help or anything yet, but it has a usage statement
and it should be clear from this email how to use it.
Thoughts? Comments?
--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
--
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
