[SSSD] New Try to build SSSD on Karmic both as of 2009.08.04

Stephen Gallagher sgallagh at redhat.com
Fri Aug 7 15:25:28 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/07/2009 10:40 AM, Miguel P.C. wrote:
> Hi again,
> 
>> International testing is always a good thing. On a related note, if you
>> would like to try your hand at translating the SSSD tools to Spanish,
>> feel free to send a patch for the server/po/es.po (you need to first run
>> 'make dist' to have it update the es.po to match the current source files.
> 
> That sounds like something I could add to my TODO list.
> May I suggest that, if we want to multiply the number of people
> translating SSSD, we can use Rosetta in Launchpad to do so. I still
> dont know hot to import ".po" into it or how to get the results from
> there but ... the translating teams behind it (I'm part of one), work
> really nice and are really accurate (although this means terrible
> discussions on one single word in the mailing lists, hehehe).
> I do appreciate the effort you are doing and maybe your policy does
> not let you do so but, I think is something worth considering.
> One thrid option, now that Launchpad is Open/Free Software you can set
> up a "Rosetta" for the project.
> 
> Sorry if I'm adding too much noise to this thread but, as I said, I
> think it's worth considering.
> 

Well, we're definitely open to expanding out translation community. Our
original plan was to use Fedora's Transifex system, but it doesn't mesh
with our development style. (Transifex requires direct access to our
upstream repository, while we prefer to receive everything in patches
that must be approved by a gatekeeper such as Simo, Sumit or myself).

The latest upstream release of Transifex supposedly has support for
patch-generation instead of repository-integration, but there is no
clear view when the Fedora Infrastructure will upgrade.

Does Rosetta have support for generating patches for upstream, or does
it require repository integration?

>> I'm glad to hear that everything is building. As I said in my previous
>> email, the prerequisites are all *supposed* to be caught by configure,
>> but the two needed for the manpages are trickier to test for. Do you
>> have any ideas how we can make configure detect whether the appropriate
>> docbook tools are in place?
> 
> No. But sounds like something interesting.
> Normally there is a file (or some) that _needs_ to be there and you
> just check for it to exist.
> (I have sure said something you all already now ...)
> 

The problem is that there's no platform-agnostic way to test for the
presence of a specific file. It could be located in any directory. For
all of the other configure tests, we're able to rely on built-in
autoconfig macros or on pkg-config.

If you have suggestions, I'm all ears :)

> M*
> _______________________________________________
> sssd-devel mailing list
> sssd-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/sssd-devel


- -- 
Stephen Gallagher
RHCE 804006346421761

Looking to carve out IT costs?
www.redhat.com/carveoutcosts/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkp8R2gACgkQeiVVYja6o6PRvwCeOjvY87fxABqU/zcM9BokEq63
YSoAn1CMhz605RWe+gvAdWPU0+0/8r1a
=pdmw
-----END PGP SIGNATURE-----



More information about the sssd-devel mailing list