Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> I don't think it's realistic to suppose that this project had strict
> processes, organization, world class documentation writers, QA etc.
I didn't disagree as to today's state;
I asked why "Sword *doesn't have to be* as professional."
A firm and deep
On Sun, 23 Sep 2007, Karl Kleinpaste wrote:
> Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> > I have noticed that for me one big problem with the Sword library is
> > poor documentation... Sword doesn't have to be as professional
>
> That's an odd supposition. Why not?
I don't think it's realisti
Eeli Kaikkonen <[EMAIL PROTECTED]> writes:
> I have noticed that for me one big problem with the Sword library is
> poor documentation... Sword doesn't have to be as professional
That's an odd supposition. Why not?
___
sword-devel mailing list: sword-d
On Sat, 22 Sep 2007, Troy A. Griffitts wrote:
> SWORD has a ton of module configuration possibilities. It is way too
> complex already. If someone is complaining that things can't be
> configured per user nicely, then they don't understand all the options
> available to them.
>
> They should at l
Sorry for not being clear in my last email... This all seem to be a
training issue. :)
I meant to say you (or a frontend) can ALREADY drop your own .conf file
in your ~/.sword/mods.d directory for each user and it will override
your globals. You don't need one per module. One file is fine:
On Sat, 22 Sep 2007, DM Smith wrote:
> I'll bite. I read the thread and I see several things being brought up:
> 1) Multi-user installs of modules.
> As I see it, the rpm or deb has a problem in that it is not managing
> permissions correctly. My suggestion is that the global sword area
> ha
I'll bite. I read the thread and I see several things being brought up:
1) Multi-user installs of modules.
As I see it, the rpm or deb has a problem in that it is not managing
permissions correctly. My suggestion is that the global sword area
have group permission of "sword" and the adm
Please, let's take the discussion into sword-devel.
On Sat, 22 Sep 2007, Hugo van der Kooij wrote:
> That sounds like the wrong way to do this. I think sword needs to redesign
> their module management to work better in multi-user environments.
>
> Hugo.
I suggest that the sword library and fron