From danielko.listas at gmail.com  Fri Apr  1 14:21:21 2011
From: danielko.listas at gmail.com (Daniel K. O.)
Date: Fri, 01 Apr 2011 12:21:21 -0600
Subject: [referencer] Basic question
In-Reply-To: <BANLkTi=-=1sgMgMU9JzfWnveE-hxx--Xnw@mail.gmail.com>
References: <AANLkTikY-akSd3fA_pHwc3U7tW2nUbyfqbkwqyAKxUo4@mail.gmail.com>	<BANLkTimv_broQ9AcUx5ktvxyj_0=JSm=nw@mail.gmail.com>	<AANLkTimGCZ6E88124QQouWB9a38W4P3i+2i_Ez85PBKd@mail.gmail.com>
	<BANLkTi=-=1sgMgMU9JzfWnveE-hxx--Xnw@mail.gmail.com>
Message-ID: <4D9617A1.9020200@gmail.com>

Em 31-03-2011 06:48, John Spray escreveu:
> If you want to learn about build systems then GNU autotools is a bad
> one to learn.  It's ubiquitous for historical reasons, not because
> there's anything beautiful about it.  If you are starting from scratch
> then you should skip autotools and learn CMake or one of the other
> more modern systems (which don't involve arcane macro languages!).  If
> you really truly want to know all about auto tools then the official
> documentation [1] is the place.  However, I can't emphasize enough
> what overwhelmingly poor use of your time it would be to do so.

Of course autotools will be the most difficult tool to learn, it is the
one that solves more problems.

I have been dealing frequently with different build systems () for a few
years now, and from my personal experience the only one that is really
reliable is GNU autotools. Finding the proper library file, to
installing (and uninstalling!) in the proper locations, cross compiling,
even something as trivial as setting compiler and linker flags, or
proper dependency tracking... most tools fail miserably at that. And
CMake is not an exception. Oh yeah, CMake DOES use an arcane macro
language too (that manages to be less readable than the mixed M4+shell
script from Autoconf.) If you don't use it then you probably could be
using a Makefile directly. Of course, if a Makefile solves your problem,
there is no reason to switch to a more complicated solution.

I really wish there was something better than autotools, but for now
I'll take it over existing alternatives any day.

-- 
Daniel K. O.
"The only way to succeed is to build success yourself."


From aaron.seilis at gmail.com  Fri Apr  1 15:09:57 2011
From: aaron.seilis at gmail.com (Aaron Seilis)
Date: Fri, 1 Apr 2011 13:09:57 -0600
Subject: [referencer] Introduction
Message-ID: <AANLkTikzgTvmruAfT2xOzETEfAFvBqU+jy8uq3CMvX_=@mail.gmail.com>

Hey all,

I'm a M.Sc. student in Canada, and I've been looking for a good tool to
manage references for my thesis. I used Referencer for a brief period,
but eventually looked elsewhere due to the lack of active maintainers.

I just finished reading the posts to the mailing list for the last few
months and I'd like to pitch-in and help. I have some experience with
C/C++/Python, but no experience with the GTK/GTKmm libraries.

After reading the posts, I'm unclear about what has been done in terms
of migration to other hosting/VCS. Does anyone have a repo available to
pull yet?

Aaron Seilis

From mads at mchro.dk  Fri Apr  1 15:23:38 2011
From: mads at mchro.dk (Mads Chr. Olesen)
Date: Fri, 01 Apr 2011 21:23:38 +0200
Subject: [referencer] Introduction
In-Reply-To: <AANLkTikzgTvmruAfT2xOzETEfAFvBqU+jy8uq3CMvX_=@mail.gmail.com>
References: <AANLkTikzgTvmruAfT2xOzETEfAFvBqU+jy8uq3CMvX_=@mail.gmail.com>
Message-ID: <1301685818.28369.16.camel@mchro-uni-laptop>

fre, 01 04 2011 kl. 13:09 -0600, skrev Aaron Seilis:
> After reading the posts, I'm unclear about what has been done in terms
> of migration to other hosting/VCS. Does anyone have a repo available
> to pull yet? 

I have converted all the branches I know of to bzr. They are all at
https://code.launchpad.net/referencer

Then I have merged everything into the
lp:~referencer-devs/referencer/shiyee_andrease_changes (1) branch,
including many of the patches I could find in launchpad.

After that, Antonio Lima has been working further on some gio porting in
his branch at lp:~referencer-devs/referencer/amrlima_gio_port, based on
(1).

I suggest you base your work on one of those branches.

I think at this point we are basically waiting for John to change the
owner of the launchpad project to the team I have created,
"referencer-devs".

-- 
Mads Chr. Olesen <mads at mchro.dk>


From aaron.seilis at gmail.com  Fri Apr  1 16:25:05 2011
From: aaron.seilis at gmail.com (Aaron Seilis)
Date: Fri, 1 Apr 2011 14:25:05 -0600
Subject: [referencer] Library Targets
Message-ID: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>

Hey all,

As you're probably all aware, there is a new major release of
gtk*/GNOME set for next week. What versions of the libraries are we
targeting? I've been able to compile against GTK+ 2.x in the past, but
GTK 3.x is going to take some work. If people want to switch to the
newer libraries, we should probably target the dev releases (they are
in a RC2 stage at the moment, so they shouldn't change much) to avoid
duplicating effort.

Aaron Seilis

From mads at mchro.dk  Fri Apr  1 16:33:32 2011
From: mads at mchro.dk (Mads Chr. Olesen)
Date: Fri, 01 Apr 2011 22:33:32 +0200
Subject: [referencer] Library Targets
In-Reply-To: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
Message-ID: <1301690012.28369.24.camel@mchro-uni-laptop>

fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
> As you're probably all aware, there is a new major release of
> gtk*/GNOME set for next week. What versions of the libraries are we
> targeting? I've been able to compile against GTK+ 2.x in the past, but
> GTK 3.x is going to take some work. If people want to switch to the
> newer libraries, we should probably target the dev releases (they are
> in a RC2 stage at the moment, so they shouldn't change much) to avoid
> duplicating effort. 

My opinion is we should try to get a release out with our gtkbuilder+gio
porting work, and then target GTK3. But the porting work to GTK3 can
probably start in a separate branch already, if someone is up for the
work :-)

-- 
Mads Chr. Olesen <mads at mchro.dk>


From amrlima at gmail.com  Fri Apr  1 17:40:39 2011
From: amrlima at gmail.com (=?ISO-8859-1?Q?Ant=F3nio?= Lima)
Date: Fri, 01 Apr 2011 21:40:39 +0000
Subject: [referencer] Library Targets
In-Reply-To: <1301690012.28369.24.camel@mchro-uni-laptop>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
	<1301690012.28369.24.camel@mchro-uni-laptop>
Message-ID: <1301694039.14309.37.camel@Gert>

Sex, 2011-04-01 ?s 22:33 +0200, Mads Chr. Olesen escreveu:
> fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
> > As you're probably all aware, there is a new major release of
> > gtk*/GNOME set for next week. What versions of the libraries are we
> > targeting? I've been able to compile against GTK+ 2.x in the past, but
> > GTK 3.x is going to take some work. If people want to switch to the
> > newer libraries, we should probably target the dev releases (they are
> > in a RC2 stage at the moment, so they shouldn't change much) to avoid
> > duplicating effort. 
> 
> My opinion is we should try to get a release out with our gtkbuilder+gio
> porting work, and then target GTK3. But the porting work to GTK3 can
> probably start in a separate branch already, if someone is up for the
> work :-)

Yes, I agree. I don't think we have the man power to port to GTK3 and
make a release soon. There's quite a lot of work done since the last
release so a release would be nice.

As for the gio port, although most of it is done, I'm having some
trouble with the Library. The xmlReadIO function takes two callback
functions and I can't make them work with Gio::FileInputStrem... If
anyone has a clue on this, let me know :).

This week and next one are busy but I'll try to hack a bit during the
weekend.

Regards,
Ant?nio Lima

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://icculus.org/pipermail/referencer/attachments/20110401/69e99a6a/attachment.pgp>

From matej.urbas at gmail.com  Fri Apr  1 18:35:25 2011
From: matej.urbas at gmail.com (Matej Urbas)
Date: Fri, 1 Apr 2011 23:35:25 +0100
Subject: [referencer] Library Targets
In-Reply-To: <1301694039.14309.37.camel@Gert>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
	<1301690012.28369.24.camel@mchro-uni-laptop>
	<1301694039.14309.37.camel@Gert>
Message-ID: <AANLkTinFROfW4FN6fg5xQWYewub3fUrXORePmQfX7oFL@mail.gmail.com>

It was me who did the libxml stuff, so I'll try to take a look at the
callbacks today.

Best,
---
Matej
On 1 Apr 2011 22:40, "Ant?nio Lima" <amrlima at gmail.com> wrote:
> Sex, 2011-04-01 ?s 22:33 +0200, Mads Chr. Olesen escreveu:
>> fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
>> > As you're probably all aware, there is a new major release of
>> > gtk*/GNOME set for next week. What versions of the libraries are we
>> > targeting? I've been able to compile against GTK+ 2.x in the past, but
>> > GTK 3.x is going to take some work. If people want to switch to the
>> > newer libraries, we should probably target the dev releases (they are
>> > in a RC2 stage at the moment, so they shouldn't change much) to avoid
>> > duplicating effort.
>>
>> My opinion is we should try to get a release out with our gtkbuilder+gio
>> porting work, and then target GTK3. But the porting work to GTK3 can
>> probably start in a separate branch already, if someone is up for the
>> work :-)
>
> Yes, I agree. I don't think we have the man power to port to GTK3 and
> make a release soon. There's quite a lot of work done since the last
> release so a release would be nice.
>
> As for the gio port, although most of it is done, I'm having some
> trouble with the Library. The xmlReadIO function takes two callback
> functions and I can't make them work with Gio::FileInputStrem... If
> anyone has a clue on this, let me know :).
>
> This week and next one are busy but I'll try to hack a bit during the
> weekend.
>
> Regards,
> Ant?nio Lima
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/referencer/attachments/20110401/47fb1038/attachment.htm>

From amrlima at gmail.com  Fri Apr  1 18:39:26 2011
From: amrlima at gmail.com (=?ISO-8859-1?Q?Ant=F3nio?= Lima)
Date: Fri, 01 Apr 2011 22:39:26 +0000
Subject: [referencer] Library Targets
In-Reply-To: <AANLkTinFROfW4FN6fg5xQWYewub3fUrXORePmQfX7oFL@mail.gmail.com>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
	<1301690012.28369.24.camel@mchro-uni-laptop>
	<1301694039.14309.37.camel@Gert>
	<AANLkTinFROfW4FN6fg5xQWYewub3fUrXORePmQfX7oFL@mail.gmail.com>
Message-ID: <1301697566.14309.38.camel@Gert>

Sex, 2011-04-01 ?s 23:35 +0100, Matej Urbas escreveu:
> It was me who did the libxml stuff, so I'll try to take a look at the
> callbacks today.
> 

Great! Thanks Matej!

> Best,
> ---
> Matej
> 
> On 1 Apr 2011 22:40, "Ant?nio Lima" <amrlima at gmail.com> wrote:
> > Sex, 2011-04-01 ?s 22:33 +0200, Mads Chr. Olesen escreveu:
> >> fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
> >> > As you're probably all aware, there is a new major release of
> >> > gtk*/GNOME set for next week. What versions of the libraries are
> we
> >> > targeting? I've been able to compile against GTK+ 2.x in the
> past, but
> >> > GTK 3.x is going to take some work. If people want to switch to
> the
> >> > newer libraries, we should probably target the dev releases (they
> are
> >> > in a RC2 stage at the moment, so they shouldn't change much) to
> avoid
> >> > duplicating effort. 
> >> 
> >> My opinion is we should try to get a release out with our
> gtkbuilder+gio
> >> porting work, and then target GTK3. But the porting work to GTK3
> can
> >> probably start in a separate branch already, if someone is up for
> the
> >> work :-)
> > 
> > Yes, I agree. I don't think we have the man power to port to GTK3
> and
> > make a release soon. There's quite a lot of work done since the last
> > release so a release would be nice.
> > 
> > As for the gio port, although most of it is done, I'm having some
> > trouble with the Library. The xmlReadIO function takes two callback
> > functions and I can't make them work with Gio::FileInputStrem... If
> > anyone has a clue on this, let me know :).
> > 
> > This week and next one are busy but I'll try to hack a bit during
> the
> > weekend.
> > 
> > Regards,
> > Ant?nio Lima
> > 
> 
> _______________________________________________
> referencer mailing list
> referencer at icculus.org
> http://icculus.org/mailman/listinfo/referencer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://icculus.org/pipermail/referencer/attachments/20110401/fba46204/attachment-0001.pgp>

From glen.shennan at gmail.com  Fri Apr  1 18:50:24 2011
From: glen.shennan at gmail.com (Glen Shennan)
Date: Sat, 2 Apr 2011 09:50:24 +1100
Subject: [referencer] Basic question
In-Reply-To: <4D9617A1.9020200@gmail.com>
References: <AANLkTikY-akSd3fA_pHwc3U7tW2nUbyfqbkwqyAKxUo4@mail.gmail.com>
	<BANLkTimv_broQ9AcUx5ktvxyj_0=JSm=nw@mail.gmail.com>
	<AANLkTimGCZ6E88124QQouWB9a38W4P3i+2i_Ez85PBKd@mail.gmail.com>
	<BANLkTi=-=1sgMgMU9JzfWnveE-hxx--Xnw@mail.gmail.com>
	<4D9617A1.9020200@gmail.com>
Message-ID: <AANLkTint0-a7sL7t4Wyk=dQydgUaWwXOeD=ZYg9zjao_@mail.gmail.com>

Well I've been through the first couple chapters of the automake manual and
it's cleared a whole lot of things up for me.  I'm happy using the build
system the way it is for the moment now, I'll learn more as the need
arises.  In my limited experience I've seen autotools most often used so I'm
happy with this one.  Thanks for the input.

On 2 April 2011 05:21, Daniel K. O. <danielko.listas at gmail.com> wrote:

> Em 31-03-2011 06:48, John Spray escreveu:
> > If you want to learn about build systems then GNU autotools is a bad
> > one to learn.  It's ubiquitous for historical reasons, not because
> > there's anything beautiful about it.  If you are starting from scratch
> > then you should skip autotools and learn CMake or one of the other
> > more modern systems (which don't involve arcane macro languages!).  If
> > you really truly want to know all about auto tools then the official
> > documentation [1] is the place.  However, I can't emphasize enough
> > what overwhelmingly poor use of your time it would be to do so.
>
> Of course autotools will be the most difficult tool to learn, it is the
> one that solves more problems.
>
> I have been dealing frequently with different build systems () for a few
> years now, and from my personal experience the only one that is really
> reliable is GNU autotools. Finding the proper library file, to
> installing (and uninstalling!) in the proper locations, cross compiling,
> even something as trivial as setting compiler and linker flags, or
> proper dependency tracking... most tools fail miserably at that. And
> CMake is not an exception. Oh yeah, CMake DOES use an arcane macro
> language too (that manages to be less readable than the mixed M4+shell
> script from Autoconf.) If you don't use it then you probably could be
> using a Makefile directly. Of course, if a Makefile solves your problem,
> there is no reason to switch to a more complicated solution.
>
> I really wish there was something better than autotools, but for now
> I'll take it over existing alternatives any day.
>
> --
> Daniel K. O.
> "The only way to succeed is to build success yourself."
>
> _______________________________________________
> referencer mailing list
> referencer at icculus.org
> http://icculus.org/mailman/listinfo/referencer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/referencer/attachments/20110402/f98ffcbc/attachment.htm>

From matej.urbas at gmail.com  Fri Apr  1 21:23:04 2011
From: matej.urbas at gmail.com (Matej Urbas)
Date: Sat, 02 Apr 2011 02:23:04 +0100
Subject: [referencer] Library Targets
In-Reply-To: <1301697566.14309.38.camel@Gert>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
	<1301690012.28369.24.camel@mchro-uni-laptop>
	<1301694039.14309.37.camel@Gert>
	<AANLkTinFROfW4FN6fg5xQWYewub3fUrXORePmQfX7oFL@mail.gmail.com>
	<1301697566.14309.38.camel@Gert>
Message-ID: <1301707385.2112.36.camel@tali.urbas.si>

Hi Antonio,

I've made a quick codeup of library reading/writing through Gio.

Please find the patch in attachments.

Is this anywhere near what you need?

Best,
---
Matej

On Fri, 2011-04-01 at 22:39 +0000, Ant?nio Lima wrote:
> Sex, 2011-04-01 ?s 23:35 +0100, Matej Urbas escreveu:
> > It was me who did the libxml stuff, so I'll try to take a look at the
> > callbacks today.
> > 
> 
> Great! Thanks Matej!
> 
> > Best,
> > ---
> > Matej
> > 
> > On 1 Apr 2011 22:40, "Ant?nio Lima" <amrlima at gmail.com> wrote:
> > > Sex, 2011-04-01 ?s 22:33 +0200, Mads Chr. Olesen escreveu:
> > >> fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
> > >> > As you're probably all aware, there is a new major release of
> > >> > gtk*/GNOME set for next week. What versions of the libraries are
> > we
> > >> > targeting? I've been able to compile against GTK+ 2.x in the
> > past, but
> > >> > GTK 3.x is going to take some work. If people want to switch to
> > the
> > >> > newer libraries, we should probably target the dev releases (they
> > are
> > >> > in a RC2 stage at the moment, so they shouldn't change much) to
> > avoid
> > >> > duplicating effort. 
> > >> 
> > >> My opinion is we should try to get a release out with our
> > gtkbuilder+gio
> > >> porting work, and then target GTK3. But the porting work to GTK3
> > can
> > >> probably start in a separate branch already, if someone is up for
> > the
> > >> work :-)
> > > 
> > > Yes, I agree. I don't think we have the man power to port to GTK3
> > and
> > > make a release soon. There's quite a lot of work done since the last
> > > release so a release would be nice.
> > > 
> > > As for the gio port, although most of it is done, I'm having some
> > > trouble with the Library. The xmlReadIO function takes two callback
> > > functions and I can't make them work with Gio::FileInputStrem... If
> > > anyone has a clue on this, let me know :).
> > > 
> > > This week and next one are busy but I'll try to hack a bit during
> > the
> > > weekend.
> > > 
> > > Regards,
> > > Ant?nio Lima
> > > 
> > 
> > _______________________________________________
> > referencer mailing list
> > referencer at icculus.org
> > http://icculus.org/mailman/listinfo/referencer
> 
> _______________________________________________
> referencer mailing list
> referencer at icculus.org
> http://icculus.org/mailman/listinfo/referencer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Referencer.libxml2_with_Gio.patch
Type: text/x-patch
Size: 7910 bytes
Desc: not available
URL: <http://icculus.org/pipermail/referencer/attachments/20110402/b625dba2/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://icculus.org/pipermail/referencer/attachments/20110402/b625dba2/attachment.pgp>

From amrlima at gmail.com  Sat Apr  2 10:54:35 2011
From: amrlima at gmail.com (=?ISO-8859-1?Q?Ant=F3nio?= Lima)
Date: Sat, 02 Apr 2011 14:54:35 +0000
Subject: [referencer] Library Targets
In-Reply-To: <1301707385.2112.36.camel@tali.urbas.si>
References: <AANLkTikdftJ2rxgUeKrcVoxgkcnXuB2+8SDrK0jTMEFs@mail.gmail.com>
	<1301690012.28369.24.camel@mchro-uni-laptop>
	<1301694039.14309.37.camel@Gert>
	<AANLkTinFROfW4FN6fg5xQWYewub3fUrXORePmQfX7oFL@mail.gmail.com>
	<1301697566.14309.38.camel@Gert>
	<1301707385.2112.36.camel@tali.urbas.si>
Message-ID: <1301756075.21660.4.camel@Gert>

S?b, 2011-04-02 ?s 02:23 +0100, Matej Urbas escreveu:
> Hi Antonio,
> 
> I've made a quick codeup of library reading/writing through Gio.
> 
> Please find the patch in attachments.
> 
> Is this anywhere near what you need?
> 

Yes! That seems to work fine! I'll test it and finish up any gnome-vfs
leftovers in the library.

Thanks!

> Best,
> ---
> Matej
> 
> On Fri, 2011-04-01 at 22:39 +0000, Ant?nio Lima wrote:
> > Sex, 2011-04-01 ?s 23:35 +0100, Matej Urbas escreveu:
> > > It was me who did the libxml stuff, so I'll try to take a look at the
> > > callbacks today.
> > > 
> > 
> > Great! Thanks Matej!
> > 
> > > Best,
> > > ---
> > > Matej
> > > 
> > > On 1 Apr 2011 22:40, "Ant?nio Lima" <amrlima at gmail.com> wrote:
> > > > Sex, 2011-04-01 ?s 22:33 +0200, Mads Chr. Olesen escreveu:
> > > >> fre, 01 04 2011 kl. 14:25 -0600, skrev Aaron Seilis:
> > > >> > As you're probably all aware, there is a new major release of
> > > >> > gtk*/GNOME set for next week. What versions of the libraries are
> > > we
> > > >> > targeting? I've been able to compile against GTK+ 2.x in the
> > > past, but
> > > >> > GTK 3.x is going to take some work. If people want to switch to
> > > the
> > > >> > newer libraries, we should probably target the dev releases (they
> > > are
> > > >> > in a RC2 stage at the moment, so they shouldn't change much) to
> > > avoid
> > > >> > duplicating effort. 
> > > >> 
> > > >> My opinion is we should try to get a release out with our
> > > gtkbuilder+gio
> > > >> porting work, and then target GTK3. But the porting work to GTK3
> > > can
> > > >> probably start in a separate branch already, if someone is up for
> > > the
> > > >> work :-)
> > > > 
> > > > Yes, I agree. I don't think we have the man power to port to GTK3
> > > and
> > > > make a release soon. There's quite a lot of work done since the last
> > > > release so a release would be nice.
> > > > 
> > > > As for the gio port, although most of it is done, I'm having some
> > > > trouble with the Library. The xmlReadIO function takes two callback
> > > > functions and I can't make them work with Gio::FileInputStrem... If
> > > > anyone has a clue on this, let me know :).
> > > > 
> > > > This week and next one are busy but I'll try to hack a bit during
> > > the
> > > > weekend.
> > > > 
> > > > Regards,
> > > > Ant?nio Lima
> > > > 
> > > 
> > > _______________________________________________
> > > referencer mailing list
> > > referencer at icculus.org
> > > http://icculus.org/mailman/listinfo/referencer
> > 
> > _______________________________________________
> > referencer mailing list
> > referencer at icculus.org
> > http://icculus.org/mailman/listinfo/referencer
> 
> _______________________________________________
> referencer mailing list
> referencer at icculus.org
> http://icculus.org/mailman/listinfo/referencer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://icculus.org/pipermail/referencer/attachments/20110402/e4abf3a0/attachment-0001.pgp>

From aaron.seilis at gmail.com  Sat Apr  2 19:39:43 2011
From: aaron.seilis at gmail.com (Aaron Seilis)
Date: Sat, 02 Apr 2011 17:39:43 -0600
Subject: [referencer] Python Dependency
Message-ID: <1301787584.1875.28.camel@localhost.localdomain>

Hey all,

I've been going through the build process and I'm wondering whether
Python is meant to actually be optional or not. I've found that with the
code as-is, it can't actually be compiled without Python (even with
Python disabled).

Regardless, on my system, I had to update configure.ac to add Python to
pkg-config for it to compile and run.

If everyone is comfortable with Python as a dependency, I will remove
the autoconf conditional tests and add Python to pkg-config.

Aaron


From matej.urbas at gmail.com  Mon Apr  4 07:56:51 2011
From: matej.urbas at gmail.com (Matej Urbas)
Date: Mon, 04 Apr 2011 12:56:51 +0100
Subject: [referencer] Python Dependency
In-Reply-To: <1301787584.1875.28.camel@localhost.localdomain>
References: <1301787584.1875.28.camel@localhost.localdomain>
Message-ID: <1301918211.3783.39.camel@tali.urbas.si>

Some very important built-in plugins are written in Python, right?

I don't mind the dependency.

On Sat, 2011-04-02 at 17:39 -0600, Aaron Seilis wrote:
> Hey all,
> 
> I've been going through the build process and I'm wondering whether
> Python is meant to actually be optional or not. I've found that with the
> code as-is, it can't actually be compiled without Python (even with
> Python disabled).
> 
> Regardless, on my system, I had to update configure.ac to add Python to
> pkg-config for it to compile and run.
> 
> If everyone is comfortable with Python as a dependency, I will remove
> the autoconf conditional tests and add Python to pkg-config.
> 
> Aaron
> 
> _______________________________________________
> referencer mailing list
> referencer at icculus.org
> http://icculus.org/mailman/listinfo/referencer

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://icculus.org/pipermail/referencer/attachments/20110404/378df30b/attachment.pgp>

From mads at mchro.dk  Mon Apr  4 07:58:22 2011
From: mads at mchro.dk (Mads Chr. Olesen)
Date: Mon, 04 Apr 2011 13:58:22 +0200
Subject: [referencer] Python Dependency
In-Reply-To: <1301918211.3783.39.camel@tali.urbas.si>
References: <1301787584.1875.28.camel@localhost.localdomain>
	<1301918211.3783.39.camel@tali.urbas.si>
Message-ID: <1301918302.3131.22.camel@mchro-uni-laptop>

man, 04 04 2011 kl. 12:56 +0100, skrev Matej Urbas:
> Some very important built-in plugins are written in Python, right?
> 
> I don't mind the dependency. 

I agree: given our limited manpower, and the fact that nobody seems to
use Referencer without Python, we should just make it a hard dependency.

-- 
Mads Chr. Olesen <mads at mchro.dk>


