a new version of mumble is out.
while attempting to use the new version, I found a few problems:
libogg should be added to depends_lib
pre-build phase no longer works (sed string replace of path to Qt)
If I can get some assistance with the Qt portion that would be smashing.
smime.p7s
Forgive me if there was a discussion of this already, but why is
universal_sysroot being removed?
http://trac.macports.org/changeset/51905
http://trac.macports.org/changeset/51907
http://trac.macports.org/changeset/51894
http://trac.macports.org/changeset/51911
On 2009-6-6 23:39, Marcus Calhoun-Lopez wrote:
Forgive me if there was a discussion of this already, but why is
universal_sysroot being removed?
Universal building doesn't need an SDK except on ppc Tiger.
- Josh
___
macports-dev mailing list
On 2009-06-05 23:25, Ryan Schmidt wrote:
All I'm saying is that the situation we have is not working. This is
not the first time someone has run port lint, thought they should
change something because port lint said it was deprecated, but this
ended up breaking the port for anyone not
I'm building a fail2ban Portfile.
fail2ban is python application.
It resides as security/py-fail2ban.
I originally had my Portfile at security/fail2ban.
I haven't created any python ports. Is there a preference in macports
for the naming of a python application?
Is so, when I change the
Is there a way to try (without dry run in trunk) to tell if a Portfile
violates the macports file structure policy?
//Brad
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On 2009-06-06 18:29, Bradley Giesbrecht wrote:
I'm building a fail2ban Portfile.
fail2ban is python application.
It resides as security/py-fail2ban.
I originally had my Portfile at security/fail2ban.
I haven't created any python ports. Is there a preference in macports
for the
On Jun 6, 2009, at 9:35 AM, Rainer Müller wrote:
On 2009-06-06 18:29, Bradley Giesbrecht wrote:
I'm building a fail2ban Portfile.
fail2ban is python application.
It resides as security/py-fail2ban.
I originally had my Portfile at security/fail2ban.
I haven't created any python ports. Is
On 2009-06-06 18:53, Bradley Giesbrecht wrote:
This doesn't seem to create a dependency on python, at least I don't
see python in port installed.
You should have python26.
I'm guessing since I didn't add a dependency on python26 ports used
Apples python to build and that might be the
On Jun 6, 2009, at 10:01 AM, Rainer Müller wrote:
On 2009-06-06 18:53, Bradley Giesbrecht wrote:
This doesn't seem to create a dependency on python, at least I don't
see python in port installed.
You should have python26.
I'm guessing since I didn't add a dependency on python26 ports used
Hi there.
For those who are in a hurry, here are Portfiles corresponding to the
brand new releases of Sip (first file) and PyQt – the latter at last
compatible with qt 4.5.1. Universal builds are supported, though of
course Sip must be built universal in order for PyQt to be.
Please test
On Jun 6, 2009, at 3:43 PM, Jordan K. Hubbard wrote:
I know that the word packaging is kind of a dirty word in MacPorts-
land (perhaps largely due to the fact that certain people just won't
stop harping about it :-), so maybe it's time for a new(er) topic in
an old conversation: Testing.
On Jun 6, 2009, at 3:43 PM, Jordan K. Hubbard wrote:
Wouldn't it be easier to simply make the creation and homing of a
testing framework a bigger priority? I've said it many times, but
I'll say it again: If someone can handle the creation part, I'm
fairly confident that the homing
You need python_select -- it allows you to change which python you use.
On Jun 6, 2009, at 1:09 PM, Bradley Giesbrecht wrote:
What is the macports way to get python26 into my paths?
smime.p7s
Description: S/MIME cryptographic signature
___
On Jun 6, 2009, at 12:50 PM, Jeff Johnson wrote:
What is the actual connection between testing and the graph you
have included?
Um. OK, sure, I'll spell it out.
1. We have a lot of ports. The number of ports we have is growing at
3-4 digit rates a year.
2. The essential mission of any
On Jun 6, 2009, at 1:01 PM, Daniel J. Luke wrote:
There have been a few attempts at this in the past - what was wrong
with them again? (I can remember at least three - your chroot build
scripts, wbb4's builds that auto generated a website that listed
failures and successes, and blb's mpab
http://portmill.florianebeling.com/ is doing a default build for all
ports if I'm not mistaken.
On Jun 6, 2009, at 4:35 PM, Jordan K. Hubbard wrote:
They all kinda worked but not well enough that nobody wanted to
actually host them anywhere since they were more clearly science
On Jun 6, 2009, at 1:31 PM, Rainer Müller wrote:
On 2009-06-06 18:32, Bradley Giesbrecht wrote:
Is there a way to try (without dry run in trunk) to tell if a
Portfile
violates the macports file structure policy?
I am not sure what you want to check for.
I want to check for violations of
On Jun 6, 2009, at 13:31, Jordan K. Hubbard wrote:
What I'm essentially proposing is that a testing harness be built
which:
1. Iterates through all Portfiles on the system, save those
explicitly marked Broken (which will be periodically swept and
marked for extermination after a short
On Jun 6, 2009, at 4:39 PM, Bradley Giesbrecht wrote:
I want to check for violations of mtree without dumping files on
disk. I'm concerned about having a mess to clean up outside mtree.
trace mode should prevent the port from writing files where it shouldn't
--
Daniel J. Luke
On Jun 6, 2009, at 12:43 PM, Jordan K. Hubbard wrote:
I know that the word packaging is kind of a dirty word in MacPorts-
land (perhaps largely due to the fact that certain people just won't
stop harping about it :-), so maybe it's time for a new(er) topic in
an old conversation: Testing.
On Sat, Jun 6, 2009 at 9:43 PM, Jordan K. Hubbardj...@apple.com wrote:
I know that the word packaging is kind of a dirty word in MacPorts-land
(perhaps largely due to the fact that certain people just won't stop harping
about it :-), so maybe it's time for a new(er) topic in an old
On Jun 6, 2009, at 11:25, Rainer Müller wrote:
On 2009-06-05 23:25, Ryan Schmidt wrote:
All I'm saying is that the situation we have is not working. This is
not the first time someone has run port lint, thought they should
change something because port lint said it was deprecated, but this
I forgot the link, but it is the one Jeremy posted already:
http://portmill.florianebeling.com/
On Sun, Jun 7, 2009 at 12:21 AM, C. Florian
Ebelingflorian.ebel...@gmail.com wrote:
On Sat, Jun 6, 2009 at 9:43 PM, Jordan K. Hubbardj...@apple.com wrote:
I know that the word packaging is kind of
On Jun 6, 2009, at 3:12 PM, William Siegrist wrote:
I suggest we setup a buildbot master at build.macports.org and have
it (at least initially) test building/installing/testing base and
ports after each commit. I think for an initial effort, in light of
all earlier attempts failing, we
On Jun 6, 2009, at 3:21 PM, C. Florian Ebeling wrote:
This has also been my view, and I have secretly been working on a
build server I call Portmill, which polls the svn, and builds every
port that changes. Results get posted to a web app which presents
them, together with build logs (tails)
Is it possible to create two launchd daemondo items with
startupitem.xx or some other intended method?
If not I suppose adding both launchd plists to port_dir/files and
using xinstall would be the macports way?
//Brad
___
macports-dev mailing
On Jun 6, 2009, at 8:54 PM, Jeremy Lavergne wrote:
I personally enjoy doing the launchd plist and avoid daemondo.
I'm kinda thinking the same thing. There is beginning to be a lot of
good Launchd examples out there and it's time consuming to try to get
daemondo to do the same things.
28 matches
Mail list logo
