[PATCHES][ELAPI] Patches to complete repo split

[Stephen Gallagher]

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

The ELAPI has been split into a new repository at
git://git.fedorahosted.org/git/ELAPI.git

This was done using 'git filter-branch' to pull the common/elapi
directory from the SSSD repository into the root of the new repository
directory. These two patches will finish the process of separating the
ELAPI from the SSSD build tree.

Patch 0001: The ELAPI no longer builds against in-tree versions of
libcollection and libini_config. This patch points the build at the
system versions of libcollection and libini_config. It also copies in
the trace.h file into the ELAPI (rather than being in a separate
dircectory above ELAPI) as well as a .gitignore file.

Patch 0002: Build the ELAPI as a shared library.
- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAktxgPQACgkQeiVVYja6o6NV6wCgorcFHCxsisVuCjv0ZbOT3NOn
> ew4AnRU1kTZ3Pjdj4ktffJgx8lpIS1qj
> =LxyU
> -----END PGP SIGNATURE-----

[Stephen Gallagher]

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

On 02/09/2010 10:36 AM, Stephen Gallagher wrote:
>  The ELAPI has been split into a new repository at
>  git://git.fedorahosted.org/git/ELAPI.git
>  
>  This was done using 'git filter-branch' to pull the common/elapi
>  directory from the SSSD repository into the root of the new repository
>  directory. These two patches will finish the process of separating the
>  ELAPI from the SSSD build tree.
>  
>  Patch 0001: The ELAPI no longer builds against in-tree versions of
>  libcollection and libini_config. This patch points the build at the
>  system versions of libcollection and libini_config. It also copies in
>  the trace.h file into the ELAPI (rather than being in a separate
>  dircectory above ELAPI) as well as a .gitignore file.
>  
>  Patch 0002: Build the ELAPI as a shared library. 
Dmitri nacked these off-list. There were two other headers that need to
be installed into /usr/include.

New patches attached.

- -- 
Stephen Gallagher
RHCE 804006346421761

Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAktxp6QACgkQeiVVYja6o6MnRQCdF2FCx7w62LU6zQ7+M6M4VT7V
> 04sAn33gJkROREpwOFsJLaDrzpVwQLUf
> =OnMC
> -----END PGP SIGNATURE-----

[Dmitri Pal]

Stephen Gallagher wrote:
>  On 02/09/2010 10:36 AM, Stephen Gallagher wrote:
>  > The ELAPI has been split into a new repository at
>  > git://git.fedorahosted.org/git/ELAPI.git
>
>  > This was done using 'git filter-branch' to pull the common/elapi
>  > directory from the SSSD repository into the root of the new repository
>  > directory. These two patches will finish the process of separating the
>  > ELAPI from the SSSD build tree.
>
>  > Patch 0001: The ELAPI no longer builds against in-tree versions of
>  > libcollection and libini_config. This patch points the build at the
>  > system versions of libcollection and libini_config. It also copies in
>  > the trace.h file into the ELAPI (rather than being in a separate
>  > dircectory above ELAPI) as well as a .gitignore file.
>
>  > Patch 0002: Build the ELAPI as a shared library.
>
>  Dmitri nacked these off-list. There were two other headers that need to
>  be installed into /usr/include.
>
>  New patches attached.
>  
I acked these two patches and pushed them last week.
I also pushed a bunch of patches that Steve provided to convert the
ELAPI build system to build on its own.

In addition to that I pushed the patches that have been pending for
months and constituted the core of the async work.

I will continue to post ELAPI patches on this list but is unclear
whether it makes sense to do since there is no enthusiasm to review them
and  I need to move on so I need to push them from time to time. I guess
we will see how it would work out. Keeping in mind that it is unclear
when I will be able to work on the code any more formal arrangement
seems problematic.


-- 
Thank you,
Dmitri Pal

Engineering Manager IPA project,
Red Hat Inc.


-------------------------------
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/