On 27 July 2016 at 06:09, Ryan Schmidt wrote:
>
> One solution that occurs to me is to define a new "preflight" phase, to be
> run before dependencies are computed. Ports can override that phase and do
> whatever checks they need and exit with "return -code error" if needed. This
> seems like th
> On Aug 4, 2016, at 2:36 PM, Clemens Lang wrote:
>
> Hi,
>
> On Thu, Jul 28, 2016 at 03:21:56AM -0500, Ryan Schmidt wrote:
>> However, as I've said, there are other reasons why a port might not be
>> able to install. Should we really modify MacPorts base and create new
>> variables to accommoda
Hi,
On Thu, Jul 28, 2016 at 03:21:56AM -0500, Ryan Schmidt wrote:
> However, as I've said, there are other reasons why a port might not be
> able to install. Should we really modify MacPorts base and create new
> variables to accommodate each of those reasons? Is there a specific
> objection to wh
> On Jul 28, 2016, at 8:36 AM, m...@macports.org wrote:
>
>
>> On Jul 27, 2016, at 6:19 PM, Ryan Schmidt wrote:
>>
>> Your suggestion seems like a variation of my "third possibility", which has
>> the disadvantages that every new reason why a port might not be installable
>> would need a new
On Jul 28, 2016, at 9:18 AM, Ken Cunningham wrote:
> OK -- So - I am absolutely nobody at all on this list, so please take this
> following idea gently.
>
> This work you're embarking on (specifying what systems a given port will
> build on, and which it won't) would seem in fact to be very si
OK -- So - I am absolutely nobody at all on this list, so please take this
following idea gently.
This work you're embarking on (specifying what systems a given port will build
on, and which it won't) would seem in fact to be very similar to what I was
getting at when I asked about the 'distrib
> On Jul 27, 2016, at 6:19 PM, Ryan Schmidt wrote:
>
> Your suggestion seems like a variation of my "third possibility", which has
> the disadvantages that every new reason why a port might not be installable
> would need a new variable introduced in MacPorts base and a new release of
> MacPo
On 2016-07-28 09:06, Artur Szostak wrote:
> This sounds like there is a need to allow encoding of version ranges. In
> which case I would suggest to solve this problem generically, to allow
> encoding version ranges in port dependencies also. Similar to what is
> possible with RPMs or Debian pac
On Jul 27, 2016, at 8:24 PM, Craig Treleaven wrote:
> On Jul 27, 2016, at 12:09 AM, Ryan Schmidt wrote:
>
>> I would like MacPorts to be extended so that it can be determined in
>> advance, from the command line, before running "port install", whether a
>> port can be installed (barring unexpe
On Jul 28, 2016, at 2:06 AM, Artur Szostak wrote:
> "... A better implementation would let the port indicate that a port builds
> on macOS 10.X or older, or macOS 10.Y or newer. ..."
>
> This sounds like there is a need to allow encoding of version ranges.
Right, *if* we make a MacPorts base f
"... A better implementation would let the port indicate that a port builds on
macOS 10.X or older, or macOS 10.Y or newer. ..."
This sounds like there is a need to allow encoding of version ranges. In which
case I would suggest to solve this problem generically, to allow encoding
version range
> On Jul 27, 2016, at 12:09 AM, Ryan Schmidt wrote:
>
> I would like MacPorts to be extended so that it can be determined in advance,
> from the command line, before running "port install", whether a port can be
> installed (barring unexpected build failures and bugs). Currently, MacPorts
> as
> On Jul 27, 2016, at 8:26 AM, m...@macports.org wrote:
>
> Hi Ryan,
>
>
>> On Jul 26, 2016, at 10:09 PM, Ryan Schmidt wrote:
>>
>> I would like MacPorts to be extended so that it can be determined in
>> advance, from the command line, before running "port install", whether a
>> port can be
Hi Ryan,
> On Jul 26, 2016, at 10:09 PM, Ryan Schmidt wrote:
>
> I would like MacPorts to be extended so that it can be determined in advance,
> from the command line, before running "port install", whether a port can be
> installed (barring unexpected build failures and bugs). Currently, Mac
I would like MacPorts to be extended so that it can be determined in advance,
from the command line, before running "port install", whether a port can be
installed (barring unexpected build failures and bugs). Currently, MacPorts
assumes any port can be installed on any system, which is not the
15 matches
Mail list logo
