Regarding http://trac.macports.org/changeset/91582, don't you also want to drop
the port:freetype dependency then?
http://trac.macports.org/changeset/91582
Also, for somebody not familiar with the build, would it be clearer to delete
the included packages then rename them with "_local"? I pre
On 4/5/12 9:53 PM, Arno Hautala wrote:
On Fri, Apr 6, 2012 at 00:15, M. Daniel Becque wrote:
I'm working on upgrading the port of Proftpd from 1.3.3c to 1.3.3g as a
first step. From the binary file repository i see where the md5 # comes
from but how do you get the sha1 and rmd160 numbers to pl
On 4/5/12 9:15 PM, M. Daniel Becque wrote:
I'm working on upgrading the port of Proftpd from 1.3.3c to 1.3.3g as a first
step. From the binary file repository i see where the md5 # comes from but how
do you get the sha1 and rmd160 numbers to place in the port file? There is
another file with eac
Can we get the Lion builders updated to XCode 4.3.2 please?
---> Configuring ffmpeg
DEBUG: Using compiler 'Mac OS X clang'
DEBUG: Executing proc-pre-org.macports.configure-configure-0
Error: Target org.macports.configure returned: XCode 4.1 cannot compile ffmpeg;
please upgrade
DEBUG: Backtrace
On Apr 5, 2012, at 23:53, Arno Hautala wrote:
> The preferred hashes are
> rmd160 and sha256.
Right. The simplest way to generate them is to remove the checksum lines from
the Portfile (or insert invalid rmd160 and sha256 checksums into the Portfile),
then run "sudo port -d checksum"; MacPorts
On Fri, Apr 6, 2012 at 00:15, M. Daniel Becque wrote:
> I'm working on upgrading the port of Proftpd from 1.3.3c to 1.3.3g as a
> first step. From the binary file repository i see where the md5 # comes
> from but how do you get the sha1 and rmd160 numbers to place in the port
> file? There is ano
I'm working on upgrading the port of Proftpd from 1.3.3c to 1.3.3g as a
first step. From the binary file repository i see where the md5 # comes
from but how do you get the sha1 and rmd160 numbers to place in the port
file? There is another file with each release, .asc, in the repository.
Thanks
D
Indeed. :-)
Can't fetch from anywhere but the distfiles mirror yet BTW; firewall
exceptions aren't in place yet. So that will cause some failures for
ports doing VCS fetches.
On 2012-4-6 11:11 , Bradley Giesbrecht wrote:
> lion :)
>
> On Apr 5, 2012, at 6:01 PM, nore...@macports.org wrote:
>
>>
lion :)
On Apr 5, 2012, at 6:01 PM, nore...@macports.org wrote:
> The Buildbot has detected a failed build on builder buildports-lion-x86_64
> while building MacPorts.
> Full details are available at:
> http://build.macports.org/builders/buildports-lion-x86_64/builds/146
>
> Buildbot URL: http:
On Thu, Apr 05, 2012 at 02:00:57PM -0500, Ryan Schmidt wrote:
> In MacPorts we would prefer to go to almost extraordinary lengths to
> use tarballs and patchfiles rather than fetching from a version
> control system. This is because we can mirror distfiles and
> patchfiles* so that in case the ups
On Apr 5, 2012, at 11:35, Chris Perl wrote:
> Has any consideration ever been given to building the vim port from
> mercurial as opposed to grabbing the tarball and applying all of the
> necessary patches on top of that?
In MacPorts we would prefer to go to almost extraordinary lengths to use
t
On Apr 5, 2012, at 10:46 AM, Aljaž Srebrnič wrote:
> On 02/apr/2012, at 19:20, Ryan Schmidt wrote:
>
>>
>> On Apr 1, 2012, at 16:16, Aljaž Srebrnič wrote:
>>
>>> I was trying to craft a port for the earthquake ruby gem (a CLI for
>>> twitter), but I stumbled on some puzzling things: apparentl
On 02/apr/2012, at 19:20, Ryan Schmidt wrote:
>
> On Apr 1, 2012, at 16:16, Aljaž Srebrnič wrote:
>
>> I was trying to craft a port for the earthquake ruby gem (a CLI for
>> twitter), but I stumbled on some puzzling things: apparently, earthquake
>> needs ruby 1.9, why is ruby available as rub
Has any consideration ever been given to building the vim port from
mercurial as opposed to grabbing the tarball and applying all of the
necessary patches on top of that?
I'm asking as I saw this thread [1] go by on vim-use. Apparently,
grabbing the tarball and applying patches doesn't necessaril
On 5 apr 2012, at 00:07, Mojca Miklavec wrote:
> Consequently I was able to create a patch with a hopefully working Qt
> terminal for gnuplot:
>https://trac.macports.org/attachment/ticket/33596/gnuplot4_6_0.diff
>
> I would be very grateful if somebody could review & test the patch
> (possibl
On 2012-4-5 17:36 , Joshua Root wrote:
> On 2012-4-5 17:26 , Blair Zajac wrote:
>> Running
>>
>> $ sudo port -f -v uninstall python32
>> $ sudo port -v install python32
>>
>> fails on the activation part:
>>
>> x ./Applications/MacPorts/Python
>> 3.2/IDLE.app/Contents/Resources/PythonCompiled.icns
On 2012-4-5 17:26 , Blair Zajac wrote:
> Running
>
> $ sudo port -f -v uninstall python32
> $ sudo port -v install python32
>
> fails on the activation part:
>
> x ./Applications/MacPorts/Python
> 3.2/IDLE.app/Contents/Resources/PythonCompiled.icns
> x ./Applications/MacPorts/Python
> 3.2/IDLE.a
Running
$ sudo port -f -v uninstall python32
$ sudo port -v install python32
fails on the activation part:
x ./Applications/MacPorts/Python
3.2/IDLE.app/Contents/Resources/PythonCompiled.icns
x ./Applications/MacPorts/Python
3.2/IDLE.app/Contents/Resources/PythonSource.icns
x ./Applications/M
18 matches
Mail list logo
