Hello everyone. I tried to make a rough python extension of libalpm but it seems that the autoconf tools in cvs only install the libs, and not the headers, like alpm.h. Is this on purpose? Or should I wait to begin develop such an extension? I am quite aware that this code is not final, and it was not my intention to distribute it or the module in anyway. I was just trying to get some work done now that needs to be done later. I'd contribute a patch but besides being autotool-illiterate I'm not sure if I'm doing anything wrong.
Thanks for your time, Joao -- A mind all logic is like a knife all blade. It makes the hand bleed that uses it.
-- Rabindranath Tagore (1861-1941)
Joao Estevao wrote:
Hello everyone. I tried to make a rough python extension of libalpm but it seems that the autoconf tools in cvs only install the libs, and not the headers, like alpm.h. Is this on purpose? Or should I wait to begin develop such an extension? I am quite aware that this code is not final, and it was not my intention to distribute it or the module in anyway. I was just trying to get some work done now that needs to be done later. I'd contribute a patch but besides being autotool-illiterate I'm not sure if I'm doing anything wrong.
You're right: alpm.h needs to be delivered, but it is the only header file in such a case. All the other ones are reserved for the library internals.
Thanks for your time, Joao -- A mind all logic is like a knife all blade. It makes the hand bleed that uses it.
-- Rabindranath Tagore (1861-1941)
pacman-dev mailing list pacman-dev@archlinux.org http://www.archlinux.org/mailman/listinfo/pacman-dev
-- Aurelien
On Thu, Oct 20, 2005 at 07:10:31PM +0200, Aurelien Foret wrote:
Joao Estevao wrote:
Hello everyone. I tried to make a rough python extension of libalpm but it seems that the autoconf tools in cvs only install the libs, and not the headers, like alpm.h. Is this on purpose? Or should I wait to begin develop such an extension? I am quite aware that this code is not final, and it was not my intention to distribute it or the module in anyway. I was just trying to get some work done now that needs to be done later. I'd contribute a patch but besides being autotool-illiterate I'm not sure if I'm doing anything wrong.
You're right: alpm.h needs to be delivered, but it is the only header file in such a case. All the other ones are reserved for the library internals.
Just cause I noticed it wasn't in CVS yet. Here's the patch.
Jason
Jason Chu wrote:
On Thu, Oct 20, 2005 at 07:10:31PM +0200, Aurelien Foret wrote:
Joao Estevao wrote:
Hello everyone. I tried to make a rough python extension of libalpm but it seems that the autoconf tools in cvs only install the libs, and not the headers, like alpm.h. Is this on purpose? Or should I wait to begin develop such an extension? I am quite aware that this code is not final, and it was not my intention to distribute it or the module in anyway. I was just trying to get some work done now that needs to be done later. I'd contribute a patch but besides being autotool-illiterate I'm not sure if I'm doing anything wrong.
You're right: alpm.h needs to be delivered, but it is the only header file in such a case. All the other ones are reserved for the library internals.
Just cause I noticed it wasn't in CVS yet. Here's the patch.
Jason
Applied. Thanks. -- Aurelien
Just cause I noticed it wasn't in CVS yet. Here's the patch.
Hello. Thx for the patch, i missed out that when autoconfized pacman-lib cvs. Sorry about that.
Regards
Christian Hamar alias krix Hungary
pacman-dev@lists.archlinux.org