Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-06 Thread mmarco
Thank you! I just made a new release with the pkg-config support El miércoles, 6 de noviembre de 2024 a las 2:14:24 UTC+1, dim...@gmail.com escribió: > Please see https://github.com/miguelmarco/libbraiding/pull/4 > > On Mon, Nov 4, 2024 at 10:06 PM mmarco wrote: > > > > I have no experience on

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-05 Thread Dima Pasechnik
Please see https://github.com/miguelmarco/libbraiding/pull/4 On Mon, Nov 4, 2024 at 10:06 PM mmarco wrote: > > I have no experience on that whatsoever, so if you could do ir (or guide me > with it), i would really appreciate it. > > El lunes, 4 de noviembre de 2024 a las 17:52:07 UTC+1, dim...@g

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-04 Thread mmarco
I have no experience on that whatsoever, so if you could do ir (or guide me with it), i would really appreciate it. El lunes, 4 de noviembre de 2024 a las 17:52:07 UTC+1, dim...@gmail.com escribió: > Hi Miguel, > > On Monday, November 4, 2024 at 10:15:01 AM UTC mmarco wrote: > > If I add a .pc

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-04 Thread Dima Pasechnik
Hi Miguel, On Monday, November 4, 2024 at 10:15:01 AM UTC mmarco wrote: If I add a .pc file to libbraiding, would it interfere with the install location in the sage distribution? as long as it's done right, it will be of help. It's a very short addition with autotools. Feel free to ask me to d

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-04 Thread mmarco
If I add a .pc file to libbraiding, would it interfere with the install location in the sage distribution? El viernes, 1 de noviembre de 2024 a las 13:44:14 UTC+1, Michael Orlitzky escribió: > On 2024-11-01 04:32:35, Nils Bruin wrote: > > There is obviously the "package version", but as I now s

Re: [sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-01 Thread Michael Orlitzky
On 2024-11-01 04:32:35, Nils Bruin wrote: > There is obviously the "package version", but as I now see, the "equivalent > system packages" don't seem to encode an explicit version restriction at > all. So I guess Michael's comment on spkg-configure.m4 is probably > appropriate. I guess explicit

[sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-01 Thread Nils Bruin
This response is more a test case in how easy it is for a sage packaging novice (me) to figure out what to do, so take this with some scepticism and some advice from experts: I did find this one: https://doc.sagemath.org/html/en/reference/spkg/libbraiding.html There is obviously the "package ve

[sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-01 Thread mmarco
How do I fix a version requirement? El viernes, 1 de noviembre de 2024 a las 8:03:28 UTC+1, Nils Bruin escribió: > On Thursday 31 October 2024 at 03:55:41 UTC-7 mmarco wrote: > > I recently released a new version of libbraiding that exposes new > functionality, in order to use those new function

[sage-devel] Re: Adding functionality that depends on upgrading a standard package.

2024-11-01 Thread Nils Bruin
On Thursday 31 October 2024 at 03:55:41 UTC-7 mmarco wrote: I recently released a new version of libbraiding that exposes new functionality, in order to use those new functions from Sage (see #38887). However, the CI tests fail because they use the old version (taken from the system, instead o