[sane-devel] unsubscriibe 11197

[gazel joel]

Le lundi 21 F=E9vrier 2005 22:05, Julien BLACHE a =E9crit=A0:
> Gerhard Jaeger  wrote:
>
> Hi,
>
> >> I'm going to play with this next week, and this will probably make it
> >> into the next revision of the Debian package, and to the CVS :)
> >
> > Hmmm, go ahead, but it should remain somewhat compatible to the current
> > hotplug stuff...
>
> I've just committed a new script to the repository, in the
> tools/hotplug-ng directory (so the current hotplug files are still
> available).
>
> The README in the directory should explain pretty much
> everything. There's a convert-usermap.sh script which will convert the
> libsane.usermap file to a file usable by the new script.
>
> I withdrew the idea of having one file per vendor ID to ease the
> package maintainers' job when dealing with external backends (like I'm
> doing with libsane-extras). Otherwise, the script works pretty much
> the way I told it would.
>
> Everyone interested, please test.
>
> JB.
>
> --
> Julien BLACHE   
>   GPG KeyID 0xF5D65169

[sane-devel] unsubscriibe 11197

[gazel joel]

Le Wednesday 23 February 2005 15:08, gazel joel a =E9crit=A0:
je rel=E8ve deux erreurs dans le champs sujet de mon pr=E9c=E9dent mail

 - unsubscriibe  alors qu'il faut lire unsugscribe avec un seul i

 - 11197 alors qu'il faut lire 111976

deux erreurs de frappe dont je vous prie de bien vouloir m'excuser

sinc=E8rement

joel.ga...@wanadoo.fr

[sane-devel] unsuubscribe 111976

[gazel joel]

Le Friday 25 February 2005 17:39, Johannes Meixner a =E9crit=A0:
> Hello,
>
> On Feb 25 09:52 m. allan noah wrote (shortened):
> > i think we want to hide the config file concept from the user
> > if possible, rather than require someone to change the perms.
>
> It is not required to change any permission.
> The default that only root can write to .conf is
> perfectly o.k. but when root likes, he can change the
> permissions for .conf so that a group of normal users
> or all normal users get write permission.
>
> Oliver's proposal hides the file concept perfectly from the user
> because the user uses only the frontend.
>
> > i personally am very much in favor of per-scanner config files
> > anyway, rather than per-backend,
>
> According to Oliver's proposal it is the backend (and as far as I
> understand it is only the backend) which writes into .conf.
> So each backend can handle its config file(s) as the backend author
> likes:
> One backend may have the configs for several scanners in one
> .conf and another backend may have .conf as
> default and ..conf, ..conf, ...
>
> > what if sane provided these config options for every user, and
> > stored them in .sane/ in their homedir.
>
> Please keep the different kind of "configs" seperated:
>
> What I have in mind when I use the word "config" are settings which
> should not be changed by a normal user during daily usage
> but only by the admin during configuration of the scanner.
> I.e. critical settings which must be set correctly because
> otherwise the scanner would not work (e.g. firmware file location)
> or may be damaged (e.g. maximum values of the scan area).
>
> What you are talking about is to store user preferences.
> A normal user likes to store often used sets of various parameters
> under convenient names like "text", "color", "photo", ...
> so that he can easily switch between them.
>
>
> Kind Regards
> Johannes Meixner
> --
> SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
> 90409 Nuernberg, GermanyWWW: http://www.suse.de/