On 02/08/12 16:13, Jeroen Demeyer wrote:
> On 2012-02-08 18:40, Jean-Pierre Flori wrote:
>> In some packages, we already have some "dependencies" section.
>> I guess this could be used (or put somewhere else in the spkg) and
>> then used by Sage (and not the spkg-install script itself, just as
>> w
On 2012-02-08 18:40, Jean-Pierre Flori wrote:
> In some packages, we already have some "dependencies" section.
> I guess this could be used (or put somewhere else in the spkg) and
> then used by Sage (and not the spkg-install script itself, just as
> what is done with SAGE_CHECK variable and spgk-c
In some packages, we already have some "dependencies" section.
I guess this could be used (or put somewhere else in the spkg) and
then used by Sage (and not the spkg-install script itself, just as
what is done with SAGE_CHECK variable and spgk-check script) to check
for dependencies.
On 8 fév, 18:
On Tue, Feb 7, 2012 at 7:47 PM, Julien Puydt wrote:
> Le mercredi 08 février, Jeroen Demeyer a écrit:
>> On 2012-02-08 04:23, Julien Puydt wrote:
>> > Le 8/2/2012, Keshav Kini a écrit :
>> >
>> >> Upstream configure scripts tend to check for dependencies by just
>> >> testing if it can use them.
On 2012-02-08 04:47, Julien Puydt wrote:
> No, you don't have spkg/standard/deps for this, as spkg/standard/deps
> is for *mandatory* packages, and the discussion was about *optional*
> packages ;-)
Maybe the best solution then is to add logic to install optional
packages to spkg/standard/deps?
-
Le mercredi 08 février, Jeroen Demeyer a écrit:
> On 2012-02-08 04:23, Julien Puydt wrote:
> > Le 8/2/2012, Keshav Kini a écrit :
> >
> >> Upstream configure scripts tend to check for dependencies by just
> >> testing if it can use them. I guess what is meant here is that
> >> spkg-install could
On 2012-02-08 04:23, Julien Puydt wrote:
> Le 8/2/2012, Keshav Kini a écrit :
>
>> Upstream configure scripts tend to check for dependencies by just
>> testing if it can use them. I guess what is meant here is that
>> spkg-install could check whether certain SPKGs had been installed
>> into the S
Le 8/2/2012, Keshav Kini a écrit :
> Upstream configure scripts tend to check for dependencies by just
> testing if it can use them. I guess what is meant here is that
> spkg-install could check whether certain SPKGs had been installed
> into the Sage installation. Also, upstream might not be awa
On 2012-02-08 01:29, John H Palmieri wrote:
>
>
> On Tuesday, February 7, 2012 3:06:14 PM UTC-8, Jeroen Demeyer wrote:
>
> I came across the following in the Sage Developer guide:
>
>- If your package depends on another package, say boehmgc, then you
> should check that thi
BTW I would also point out that all these dependency problems are basically
solved in Burcin's `lmonade` repackaging of Sage, in case anyone reading
this is not aware of that excellent project.
.. lmonade_: http://www.lmona.de/
-Keshav
Join us in #sagemath on irc.freenode.net !
--
To po
On 2012-02-08 12:22, Keshav Kini wrote:
> Upstream configure scripts tend to check for dependencies by just
> testing if it can use them. I guess what is meant here is that
> spkg-install could check whether certain SPKGs had been installed into
> the Sage installation.
The upstream configure scri
Upstream configure scripts tend to check for dependencies by just testing
if it can use them. I guess what is meant here is that spkg-install could
check whether certain SPKGs had been installed into the Sage installation.
Also, upstream might not be aware of certain dependencies it might gain b
Le 7/2/2012, John H Palmieri a écrit :
> This is relevant for optional packages, so maybe it should say:
>
> If your package depends on an optional package, say ..., then you
> should
>
> As Dima points out, Simon King's group cohomology package does
> something like this.
>
> Is the 'de
On Tuesday, February 7, 2012 3:06:14 PM UTC-8, Jeroen Demeyer wrote:
>
> I came across the following in the Sage Developer guide:
>
>- If your package depends on another package, say boehmgc, then you
> should check that this other package has been installed. Your
> ``spkg-install``
On Wednesday, February 8, 2012 7:06:14 AM UTC+8, Jeroen Demeyer wrote:
>
> I came across the following in the Sage Developer guide:
>
>- If your package depends on another package, say boehmgc, then you
> should check that this other package has been installed. Your
> ``spkg-install
As the PPL packager I'm fine with this ;-)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http:/
16 matches
Mail list logo
