[arch-general] Daemon Locale

2011-11-23 Thread Yclept Nemo
I want to create a new postgresql database cluster with UTF-8 locale
and default (template) encoding. While initdb, run by rc.d/postgresql,
inherits the locale from the environment, rc.d/functions overrides the
locale to C as specified by DAEMON_LOCALE

So I am thinking, is there any reason why not to run all daemons as
UTF-8? I remember in the mailing list some devs preferred to run with
the C locale. Why?

Alternatively I could run initdb myself.. I am also wondering if
starting a cluster with a different encoding than that of the
environment (UTF-8 in a C environment) will cause problems

thanks,


Re: [arch-general] [arch-dev-public] Developer / TU key signing, first master key available

2011-11-23 Thread Marek Otahal
On Wednesday 23 of November 2011 17:12:44 Pierre Schmitz wrote:
> I created a graph of our web of trust as it looks now (using sig2dot;
> thanks Dan):
>   https://users.archlinux.de/~pierre/tmp/sigs.png 
I'm not sure how the graph should work, but it shows eg. Thomas B. three times! 
:)
-- 

Marek Otahal :o)

signature.asc
Description: This is a digitally signed message part.


Re: [arch-general] Automatic File Associations Alloting

2011-11-23 Thread Jayesh Badwaik
EDIT: Int the above post, check the box means checks the always opens box?
--
Cheers and Regards
Jayesh Vinay Badwaik
Electronics and Communication Engineering
VNIT, INDIA
-





On Wed, Nov 23, 2011 at 10:08 PM, Jayesh Badwaik
 wrote:
> Hi,
>
> All the programs, mimeo, xdg-open are oriented towards using mime info
> to open application. My problem is different. What I want is a way to
> tell "my" desktop environment or whatever to use which applications.
>
> The main issue is as follows.  Every program that gets installed can
> do anything to the mimeinfo.list file. Sometimes, it will also change
> the xdg-open values. There are multiple systems with multiple
> standards. We cannot do much about that. However, what we can do is,
> we can make it easy to create an interface to program that.
>
> My suggestions is as follows.
> All file associations would be stored in a XML based file. There will
> be other details in it. But the main details is as follows
> 1. mime-type
> 2. associated applications wuth priority starting from 1. Why exactly
> one, will be clear later.
>
> Now whenever a new package is installed. It will contain an XML file
> containing description of the mimetype in the same manner. When the
> package is installed, the file will be transferred to a folder. The
> main file which contains the descriptions of the mime type will be
> somewhere else. This folder will contain the mime files which have not
> yet been incorportated into the main file.
>
> Now, a program would run which will take this folder and the original
> file as the default arguments and then update the file types. If there
> is a conflict, especially if the priority of the application for the
> mime type is already taken, then there can be a ncurses based
> resolution window, letting window resolve the conflict (modeled on the
> file association selectors in Windows applications). The priority in
> the package files can be -1 if the file wants to go to the last
> priority if possible. (like the nice factor of the processes)
>
> But no one can occupy the priority zero. Suppose a user opens an app
> using open with command and then checks the box, then automatically an
> entry is created in the folder with priority zero and then it is
> updated. This way, automatic software will never trump the user set
> defaults under any circumstances and the conflict management would
> prevent the irritation at the file open time. I am sure people are
> more careful during install than they are during file opening.
>
> Now the final XML file is created. This file can be then modified into
> whatever is demanded by any DE etc etc. What do you think?
>
>
> --
> Cheers and Regards
> Jayesh Vinay Badwaik
> Electronics and Communication Engineering
> VNIT, INDIA
> -
>
>
>
>
>
> On Wed, Nov 23, 2011 at 3:45 PM, SanskritFritz  
> wrote:
>> Since mimeo also supports file uris now, there is no need to change
>> this package anymore.
>


Re: [arch-general] Automatic File Associations Alloting

2011-11-23 Thread Jayesh Badwaik
Hi,

All the programs, mimeo, xdg-open are oriented towards using mime info
to open application. My problem is different. What I want is a way to
tell "my" desktop environment or whatever to use which applications.

The main issue is as follows.  Every program that gets installed can
do anything to the mimeinfo.list file. Sometimes, it will also change
the xdg-open values. There are multiple systems with multiple
standards. We cannot do much about that. However, what we can do is,
we can make it easy to create an interface to program that.

My suggestions is as follows.
All file associations would be stored in a XML based file. There will
be other details in it. But the main details is as follows
1. mime-type
2. associated applications wuth priority starting from 1. Why exactly
one, will be clear later.

Now whenever a new package is installed. It will contain an XML file
containing description of the mimetype in the same manner. When the
package is installed, the file will be transferred to a folder. The
main file which contains the descriptions of the mime type will be
somewhere else. This folder will contain the mime files which have not
yet been incorportated into the main file.

Now, a program would run which will take this folder and the original
file as the default arguments and then update the file types. If there
is a conflict, especially if the priority of the application for the
mime type is already taken, then there can be a ncurses based
resolution window, letting window resolve the conflict (modeled on the
file association selectors in Windows applications). The priority in
the package files can be -1 if the file wants to go to the last
priority if possible. (like the nice factor of the processes)

But no one can occupy the priority zero. Suppose a user opens an app
using open with command and then checks the box, then automatically an
entry is created in the folder with priority zero and then it is
updated. This way, automatic software will never trump the user set
defaults under any circumstances and the conflict management would
prevent the irritation at the file open time. I am sure people are
more careful during install than they are during file opening.

Now the final XML file is created. This file can be then modified into
whatever is demanded by any DE etc etc. What do you think?


--
Cheers and Regards
Jayesh Vinay Badwaik
Electronics and Communication Engineering
VNIT, INDIA
-





On Wed, Nov 23, 2011 at 3:45 PM, SanskritFritz  wrote:
> Since mimeo also supports file uris now, there is no need to change
> this package anymore.


Re: [arch-general] Automatic File Associations Alloting

2011-11-23 Thread SanskritFritz
On Wed, Nov 23, 2011 at 6:12 AM, Jayesh Badwaik
wrote:

> > xdg-open? Xyne wrote mimeo to help manage mime-types, been using that
> > with xdg-utils-mimeo from the AUR for a while now...
> >
>

xdg-utils-mimeo is orphaned in the aur, and some comments suggest that is
is not needed anymore:
> Comment by: xduugu on Sun, 13 Mar 2011 23:12:21 +
>Since mimeo also supports file uris now, there is no need to change
this package anymore.

Is this true? I'm just starting to learn mimeo and associations in general,
seems pretty complicated for me.


[arch-general] Re: pacman new generation

2011-11-23 Thread Nicolas Sebrecht
The 22/11/11, Norbert Zeh wrote:

> but it's not an easy language to
> learn to use effectively.  For that reason, the pool of Haskell developers out
> there is much smaller than the pool of C programmers.  Furthermore, from my 
> own
> experience I know that writing good Haskell code poses its own set of 
> challenges

Agreed. I don't think Haskell is the best language for the purpose.
Go language may fit much better.

-- 
Nicolas Sebrecht