> Which maintainer names in Portfile should we look for?
So sorry:
jeremy is snc
michael is michaelld
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mai
Which maintainer names in Portfile should we look for?
Blair
On Dec 11, 2011, at 6:23 PM, Michael Dickens wrote:
> I'm also in a situation where anyone wanting my maintained ports is welcomed
> to them -- just let me know. - MLD
>
> On Dec 11, 2011, at 9:05 PM, Jeremy Lavergne wrote:
>
>> Fo
In answer to your question:
1. Portable Standard Lisp (PSL) is currently the Lisp used most widely for
running REDUCE. PSL is supported on many architectures and is an ideal system
for those wanting to run REDUCE as a standalone system. Currently, TeXmacs has
a plugin for psl reduce. If you use
I'm also in a situation where anyone wanting my maintained ports
is welcomed to them -- just let me know. - MLD
On Dec 11, 2011, at 9:05 PM, Jeremy Lavergne wrote:
For any newer maintainers, or people interested in becoming
maintainers, I happily open my maintainer list: if you find
any you
For any newer maintainers, or people interested in becoming maintainers, I
happily open my maintainer list: if you find any you like let me know.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.ma
On Dec 11, 2011, at 19:33, Mark Brethen wrote:
> I have a working portfile (included below) and verified that the psl variant
> builds. The user has two options : 1) Build Reduce using the CSL Lisp system
> [default] or 2) using the PSL Lisp system [variant]. Is this the preferred
> way of usi
I have a working portfile (included below) and verified that the psl variant
builds. The user has two options : 1) Build Reduce using the CSL Lisp system
[default] or 2) using the PSL Lisp system [variant]. Is this the preferred way
of using a variant?
At present "make install" is deeply broke
On Mon, Dec 12, 2011 at 01:58:21AM +0100, Clemens Lang wrote:
> Licensed GPL: keyanalyze
To avoid any confusion, that should have been GPL-2, as mentioned in the
source:
> [1]
> http://packages.debian.org/changelogs/pool/main/s/signing-party/signing-party_1.1.4-1/signing-party.copyright
S
On Sun, Dec 11, 2011 at 06:39:23PM -0600, Ryan Schmidt wrote:
> Oh right, I thought you were listing "and" licenses but you were
> listing "or" licenses. No change then. I'm not aware of any problems
> listing the licenses this way.
Now that you mention it, that might have been the wrong notation.
> Oh right, I thought you were listing "and" licenses but you were listing "or"
> licenses. No change then. I'm not aware of any problems listing the licenses
> this way.
"2+" still sounds best here, since it implies the "or" for all values below.
Whether we interpret the logic appropriately is
> The signing-party port contains some software licensed under BSD, some
> licensed under GPL-2 and some under GPL-2 or any later version. I think
> this representation is closest to reality, as you can't just distribute
> the whole package under the terms of GPL-3 (which would be possible if I
> d
On Dec 11, 2011, at 18:20, Clemens Lang wrote:
> On Sun, Dec 11, 2011 at 06:13:58PM -0600, Ryan Schmidt wrote:
>>> +license {BSD GPL-2+ GPL-2}
>>
>> I think there's no point listing GPL-2 if you're already listing GPL-2+. "2"
>> is included in "2 or greater".
>
> The signing-party p
r87905 was a quick fix for these build failures. It's better to have things
building than not.
We should revert r87905 once #31827 is fixed.
On Dec 11, 2011, at 4:15 PM, Ryan Schmidt wrote:
>
> On Dec 11, 2011, at 17:18, jerem...@macports.org wrote:
>
>> Revision: 87905
>> http://tra
On Sun, Dec 11, 2011 at 06:13:58PM -0600, Ryan Schmidt wrote:
> > +license {BSD GPL-2+ GPL-2}
>
> I think there's no point listing GPL-2 if you're already listing GPL-2+. "2"
> is included in "2 or greater".
The signing-party port contains some software licensed under BSD, some
licen
On Dec 6, 2011, at 23:48, jamesk...@macports.org wrote:
> Revision: 87808
> http://trac.macports.org/changeset/87808
> Author: jamesk...@macports.org
> Date: 2011-12-06 21:48:36 -0800 (Tue, 06 Dec 2011)
> Log Message:
> ---
> Added client for nova api
>
> Added Paths:
> --
On Dec 11, 2011, at 17:18, jerem...@macports.org wrote:
> Revision: 87905
> http://trac.macports.org/changeset/87905
> Author: jerem...@macports.org
> Date: 2011-12-11 15:18:23 -0800 (Sun, 11 Dec 2011)
> Log Message:
> ---
> Set GI_SCANNER_DISABLE_CACHE when building, see #
On Dec 11, 2011, at 16:12, c...@macports.org wrote:
> Revision: 87904
> http://trac.macports.org/changeset/87904
> Author: c...@macports.org
> Date: 2011-12-11 14:12:51 -0800 (Sun, 11 Dec 2011)
> Log Message:
> ---
> signing-party: License
>
> Modified Paths:
> ---
It looks like the latest svn already includes PSL. This is from the read me:
Status report January 2011
==
PSL
---
We have the PSL sources in the trunk cleaned up for the most
wanted versions, i.e. Windows, Linux(Intel), and Mac/OS (Intel)
both 32 and 64 bit.
The mainte
On Dec 11, 2011, at 13:06, Mark Brethen wrote:
> I was developing a port a couple months back for Reduce Algebra. Recently I
> received some feedback below about the installation on linux and it was
> pretty simple. Any reason it should not be the same for Mac?
>
> ###
>
> -Mark
>
> Begin fo
I was developing a port a couple months back for Reduce Algebra. Recently I
received some feedback below about the installation on linux and it was pretty
simple. Any reason it should not be the same for Mac?
###
-Mark
Begin forwarded message:
> From: "Andrey G. Grozin"
> Date: December 11,
20 matches
Mail list logo