Re: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread Jeroen Demeyer
On 2014-01-27 22:11, François Bissey wrote: We are still at putting all the building blocks in place. Good. What I've said boils down to: don't rush to add the first building blocks if the building isn't drawn yet. Especially with git branches, it's easy enough to develop a branch and only merg

Re: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread François Bissey
On Mon, 27 Jan 2014 21:47:37 Jeroen Demeyer wrote: > On 2014-01-27 20:40, David Roe wrote: > > there's active work on using it for other packages. > > Ticket numbers please... I guess that's a bit over-enthusiastic of David. We are still at putting all the building blocks in place. I guess the nex

Re: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread Jeroen Demeyer
On 2014-01-27 20:40, David Roe wrote: there's active work on using it for other packages. Ticket numbers please... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email t

Re: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread David Roe
I vote [*] Yes. I think it's okay to add it now since there's active work on using it for other packages. David On Mon, Jan 27, 2014 at 6:33 AM, Jeroen Demeyer wrote: > On 2014-01-27 12:40, Volker Braun wrote: > >> This is the obligatory "new spkg" vote... >> > I vote for > > [*] Yes, make the

RE: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread Francois Bissey
] Pkgconfig as standard spkg One general problem with combining libraries into larger projects is that * the package providing of the library knows best about the necessary compiler/linker flags, but * packages using the library must specify the compiler/linker flags Pkgconfig is the standard for solving

Re: [sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread Jeroen Demeyer
On 2014-01-27 12:40, Volker Braun wrote: This is the obligatory "new spkg" vote... I vote for [*] Yes, make the package standard. However, wait until the functionality is actually used by some package (no point in shipping it now since nothing in Sage needs it). -- You received this message

[sage-devel] Pkgconfig as standard spkg

2014-01-27 Thread Volker Braun
One general problem with combining libraries into larger projects is that * the package providing of the library knows best about the necessary compiler/linker flags, but * packages using the library must specify the compiler/linker flags Pkgconfig is the standard for solving this problem, htt