On 20 May 2014, at 01:10 , Ryan Schmidt wrote:
> I undid the revbump, to save users from needlessly reinstalling the port if
> they haven't already.
Oh, thanks, Ryan!
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosfor
Hi Ryan,
On 20 May 2014, at 01:01 , Ryan Schmidt wrote:
> Yeah, it's good if commit messages can explain why a change is being made.
Yes, I know. Was a little to fast there, i admit.
> Just saying that you're revbumping a port isn't informative; I'd like to be
> able to see e.g. which library h
On 20 May 2014, at 00:30 , Ryan Schmidt wrote:
> On May 19, 2014, at 13:50, m...@macports.org wrote:
>> tiff: revbump needed
> Why did it need a revbump?
I see now that my rebump didn’t actually help, since even with the freshly
rev-bumped tiff I once again get a rebuild of tiff on another VM:
Hi Ryan,
On 17 May 2014, at 01:26 , Ryan Schmidt wrote:
> I don't recall. Can you find where Bradley said that before? Mailing list
> post, etc.?
I’ve contacted him, since I cannot find his post, but I am quite sure he said
it a while ago.
> Have you checked whether dbus works correctly, on a
Hi,
when setting up a new MacPorts installation I noticed reading dbus’ notes:
---
$ port notes dbus
dbus has the following notes:
# Startup items have been generated that will aid in
# starting dbus with launchd. T
At least these two were needed here on my end:
—
$ sudo chmod o+r /opt/local/libexec/macports/lib/tcl8.5/.
$ sudo chmod o+r /opt/local/libexec/macports
—
but it looks like /opt/local/libexec/macports/lib/tcllib1.15
—
drwxr-x--x 111 root admin3774 May 11 16:22 tcllib1.15
—
is another candidate.
Hi Joshua,
when trying to run mpstats submit I met a problem which is caused by the
current RC1.
On 11 May 2014, at 23:44 , Clemens Lang wrote:
> It seems your tcl8.5 directory isn't readable by your user. Which user did
> you use
> to install it? Which umask was set while you installed it? Wh
Hi devs,
wouldn’t it be nice to have a “ticket” command for port?!
I am wondering whether this has been already suggested or not…
I am imagining the following:
1) Something like
—
$ port ticket foo
—
could open up the web browser and show all trac tickets for port foo.
2) Even better woul
Hi Clemens,
this is what I get since I installed the current RC:
—
$ /opt/local/libexec/mpstats submit
Error: couldn't read file
"/opt/local/share/macports/Tcl/macports1.0/macports_fastload.tcl": no such file
or directory
—
Luckily I had seen http://trac.macports.org/changeset/119760 so that I
Hi Michael,
On 07 May 2014, at 02:51 , Michael Dickens wrote:
> Given the ticket's info that you provided it will definitely be fixed
> in the Qt 4.8.6 release
yes, I know. That was the first thing I tested and which made me write my post
in the first place. ;-)
Thanks again,
Marko
__
Hi Michael and contributors,
thanks so much for this upgrade!!! It’s awesome how you take care of Qt4!
I appreciate that so much, because it is an essential library for KDE as well,
which I am interested in.
This surely not only resolved long lived little annoyance [1].
Thanks again,
Marko
On 02 May 2014, at 21:12 , Clemens Lang wrote:
> Maybe it depends on the comment content?
I couldn’t figure it out where it was, but it must have been some invisible
character which wasn’t really deleted.
The only idea how it might have happened is that I had tried to input a “TM"
symbol at s
On 02 May 2014, at 21:12 , Clemens Lang wrote:
> Maybe it depends on the comment content? Did you try adding a comment with
> a different text?
Ha, thanks, why didn’t I think of that now…
It worked.
So, I have to rewrite my message and see.
signature.asc
Description: Message signed with OpenPGP
Hmmm, you could add a comment? I see you could...
Well, yes, I was logged on with my handle. Used Safari and Firefox and both
gave and still give me this error!
Greets,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
ma
Hi Shree,
when I tried to add a comment to a ticket [1] I just got the response “Trac
Error” from MacPorts trac.
Since this happened a couple of times within the last 2 hrs or so I guess
something is wrong on the server side, because switching to another web client
didn’t help either.
Greets,
Hi Frank,
thanks for pointing that out. I wasn’t aware of the stub!
I’ve reopened the ticket and am awaiting input from the portfile author.
Thanks again,
Marko
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
macports-dev ma
I am not sure whether it had been already said, but I think it would be nice to
let query list also generate links to the port’s home URL, which holds just as
well for the MacPorts port list!
___
macports-dev mailing list
macports-dev@lists.macosforge.o
Dear Ryan,
thanks for your attentive eye, as always!
I am sorry I committed such messy ports with rkward(-devel), but I just
committed what I got from the original authors. I see now that the discussion
you had back then in [1] didn’t produce a fully MacPorts-satisfying portfile.
Well, I’ll tr
Hi Joshua,
On 14 Apr 2014, at 10:56 , Joshua Root wrote:
> Dependents are precisely those ports that are needed at runtime. We
OK, it’s not inconsistent, I see that now.
Good, have to check on this again, once kdelibs4’s dependency on nepomuk and
thus openssl is gone.
> You maybe want something
On 14 Apr 2014, at 02:09 , Ryan Schmidt wrote:
> These answers are in the OS X Mavericks software license agreement:
Thanks so much for your citation. I have stolen them right away and replanted
them on [1]
>> - How can he get in contact with the MacPorts CI guys?
> admin at macosforge dot or
On 14 Apr 2014, at 02:07 , Brandon Allbery wrote:
> rev-upgrade catches these silent errors and corrects them.
I know that it does that. I’ve often run into traps like that in the past and
it’s so much better now with rev-upgrade in place taken care of all of that. :-)
_
On 14 Apr 2014, at 01:52 , Ryan Schmidt wrote:
> By definition, a build dependency isn’t needed at runtime, so you wouldn’t
> distribute it, so you wouldn’t care about build dependencies’
> distributability, would you?
Hmmm, you’ve got your point.
When I was writing those lines I awaited this k
Hi Ryan,
On 14 Apr 2014, at 01:51 , Ryan Schmidt wrote:
> If a binary on our packages server is mislinked (i.e. linked with a previous
> version of a dependency’s library) such that rev-upgrade decides to rebuild
> it, we should revbump to fix the binary package.
OK.
> However, I looked at one
Hi Ian,
I just want to add something as well as answer some of your questions (with
what I found via Google).
On 13 Apr 2014, at 23:06 , Ian Wadham wrote:
> Ben is not sure what would be required to set up CI of KDE in an Apple
> OS X envirionment. His immediate questions are to do with Apple
On 13 Apr 2014, at 21:12 , Joshua Root wrote:
> What would this warning say, and where would it go? And have you read
> the help for port rdeps?
Ah, sorry, now I see that there is indeed an option "--no-build" there.
But still, one could make use of an option like “--with-build” for the
rdepend
Hi devs,
I have found [1-6] discussing how licenses are being handled on MacPorts.
Browsing our Guide I couldn’t find any section containing license rules.
According to [7] we’ve got only port_binary_distributable.tcl [8] as some sort
of license documentation.
Shouldn’t we have more that our Gui
On 13 Apr 2014, at 19:08 , Jeremy Lavergne wrote:
> Using verbose (port -v) might list out the types of dependencies.
The only difference I can see here is that the -v version puts “port:” in front
of the port names…
What am I missing?
—
$ port deps gtk2
Full Name: gtk2 @2.24.23_0+x11
Extract De
On 13 Apr 2014, at 18:01 , Brandon Allbery wrote:
> Well, this is still highlighting an inconsistency.
Yes, right you are, otherwise I wouldn’t have stumbled over it.
> In this case, I think it's between the actual record of dependencies in the
> package registry (produced by actually installing
Yesterday I noticed - while installing a MacPorts from scratch - that after all
the port tiff got rebuild by rev-upgrade.
Looks like tiff would need a revbump right?
How is the policy regarding such cases??
Shall one simply commit a revbump whenever one spots a port like that
On 13 Apr 2014, at 17:46 , Brandon Allbery wrote:
> Looks like it's because it's a build dependency --- so, while the gtk2 port
> is what pulled it in, it is not needed at runtime.
Ahhh, I see.
Thanks for solving this mystery! :-)
Greets,
Marko
___
mac
Hi,
port gtk-doc puzzled me just now, since it doesn’t seem to have dependent ports.
—
$ port rdependents gtk-doc
gtk-doc has no dependents.
—
But if I let port show me all kmymoney4-devel deps it gets listed:
—
$ port rdeps kmymoney4-devel
...
kde4-runtime
kdelibs4
soprano
li
Hi Eric,
> #!/bin/sh
> for depport in `port -q rdeps $1`; do
> sh /path/to/mp-distributable.sh ${depport}
> done
that worked like a breeze. I should have been able to create in on my own. :-)
Thanks!
Greets,
Marko
___
macports-dev ma
Hi devs,
I just wonder whether someone out there
has already written some script
which can determine for any given port A
whether non-binary ports B1-Bn are to be build during
port A's installation.
Greets,
Marko
P.S.: I do know that there is mp-d
Hi Eric,
thanks for letting me know about those two tickets, to which I CC’ed myself
just now. :-)
I am not so sure that you can actually INSTALL all tests with any software…
independent on whether you actually might now want to do that. The
two-step-install I use with "kmymoney4-devel +tests"
On 21 Mar 2014, at 00:14 , Ryan Schmidt wrote:
> I’m not aware of any ports that do that, or any tests that are designed to
> work that way.
Only recently I came across the "test phase” which can be defined in a portfile.
I’ve introduced properly running tests for kmymoney4-devel with r118839.
On 10 Apr 2014, at 22:09 , Jeremy Lavergne wrote:
> You probably need add a local repo with higher priority, such as:
Looks like it. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports
Hi MP devs,
currently I have to have patch [1] in place to be able to successfully install
qmake-based ports.
The problem is now that during "sudo port selfupdate” all these changes get
reverted.
How can I keep my needed patches for MacPorts base without the need to re-patch
base after the se
Hi Ryan,
I do like your work very much! This looks really cool!!!
A few remarks:
1) Perhaps the icons at least could be blue to match the mandatory
good-old MacPorts icon, which definitely needs to appear here instead of the
new “macports”. :)
2) I think that the headline is p
I also had problems with the git upgrades every now and then. Just a give it
some time and then all will run smoothly.
(Have no idea why it happens, though. Perhaps an issue with some mirrors… )
I usually tried some hours later once again.
___
macports-
Hi Brad,
On 27 Mar 2014, at 00:14 , Bradley Giesbrecht wrote:
> Marko, do you have a link to the KDE-MAC mailing list subscription page?
> I was unaware that KDE had a Mac specific list.
Unfortunately it’s a VERY LOW VOLUME mailing list:
https://mail.kde.org/mailman/listinfo/kde-mac
:-
On 27 Mar 2014, at 00:26 , Ryan Schmidt wrote:
> https://trac.macports.org/ticket/41321
Thanks, Ryan, for pointing this out.
I see the post is already 4 months old… So, I was obviously just lucky that I
hadn’t run into this earlier already.
Greets,
Marko
___
I have built kmymoney4-devel’s sources without using ports, but simply did a
“cd kmymoney; mkdir build; cd build; cmake ..; make” and it turned out that
cmake ran through with a few warnings and the build finished successfully after
all.
So, that the build without “sudo port build” does not wo
Dear devs, maintainers, users,
I want to cite an invitation from Mario Fux from the KDE community posted on
the KDE-MAC mailing list:
Mario Fux wrote:
... I'm currently organizing the next edition of the Randa Meetings. The dates
are set: Saturday, 9th to Friday, 15th of August. But we're s
I hadn’t built kmymoney4-devel for a while since there had been little progress
in development.
But now that I tried it again I had to realise that it suddenly doesn’t build
anymore.
Obviously it doesn’t even configure properly...
Here is what I saw:
—
.
.
.
:info:configure -- Results of Search
On 22 Mar 2014, at 18:01 , Ryan Schmidt wrote:
> On Mar 22, 2014, at 11:51, mk-macpo...@techno.ms wrote:
>> do MacPorts’ buildbots also build all debug variants of the various ports,
>> or only the default variant of every port?
> Only default variants.
I was afraid to hear that. :-)
Had some hop
HI devs,
do MacPorts’ buildbots also build all debug variants of the various ports, or
only the default variant of every port?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/m
On 21 Mar 2014, at 00:14 , Ryan Schmidt wrote:
> I’m not aware of any ports that do that, or any tests that are designed to
> work that way.
OK, in just now I have made it work by simply chown'ing the port’s work
directory and executing ctest by the logged in user.
That finally did the job.
(A
I would like to introduce a tests variant for a port.
Can someone point me to a port which successfully installs a test variant?
I know that I can build and run tests when building ports (i.e. when I only run
“sudo port build; cd build; ctest …”).
But I want that all needed test files get actua
Hi MacPorts devs,
how is the schedule for release of the next MP release which will - I gather -
include the opt-in-able mpstats?
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinf
On 16 Mar 2014, at 21:07 , Rainer Müller wrote:
> I am afraid of the increased complexity of git and the changing workflow for
> other
> developers.
>
> We cannot simply swap out Subversion and bless a git mirror as the new
> main ports tree, a new way of working with git has to be worked out f
On 16 Mar 2014, at 19:42 , Sean Farley wrote:
> I would suggest Mercurial.
+1
But, in order to avoid any flamewars: I’d be going for git as well, if it would
win in an election. :-)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https
Hi Clemens,
thanks for the quick response.
I have done as requested, but that seems to lead to another problem:
—
$ ./testgraphical
file:///Users/marko/projects/TestGraphical/build/src/testgraphical.app/Contents/MacOS/:
File not found
Killed: 9
—
But I guess that could be due to the applicatio
Hi Clemens,
thanks for the quick response.
I have done as requested, but that seems to lead to another problem:
—
$ ./testgraphical
file:///Users/marko/projects/TestGraphical/build/src/testgraphical.app/Contents/MacOS/:
File not found
Killed: 9
—
But I guess that could be due to the applicatio
Hi,
I am testing KDevelop a little.
After a short hiccup I was able to get a scaffold for a “graphical app”
automagically built fine! :)
But the real problem starts when trying to run the app:
—
$ ./testgraphical.shell
dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from:
/Sys
From: mk-li...@email.de
Subject: Re: Running KDE apps on Apple OS X
Date: 11 Mar 2014 23:05:09 GMT+1
To: KDE-devel Mailing-List
Cc: KMyMoney KDE Development List , Developer-MacPorts
Mailing-List
Hi Ian,
thanks for your initiative!!!
I am not a software engineer - but just a Linux/MacOSX hobb
Hi Vincent,
I am myself waiting for a fix for this since a while.
Can you perhaps make your updated Portfile public, e.g. below [1] or [2].
I am willing to test (by building the port for a few hours) whether the upgrade
works seamlessly on my end before rolling it out to everyone.
Greets,
Marko
Hi Josh,
On 17 Feb 2014, at 07:35 , Joshua Root wrote:
> You don't have to sync your ports tree with svn just because you're
> using the trunk version of base.
Oh, I see!
:)
That means I misunderstood Clemens’ statement:
On 10 Feb 2014, at 12:01 , Clemens Lang wrote:
> … Note that selfupdate w
Hi Ryan,
On 17 Feb 2014, at 05:10 , Ryan Schmidt wrote:
> What risk are you envisioning?
I fear the risk of switching to an SVN port tree and having to go back to an
rsync’ed one in case I need to...
Or would that be piece of cake?
Well, I can imagine that it could be troublesome to perform this
> At that point, it might take as long as a reboot depending on your build: but
> you should achieve the same outcome.
I guess you’re right. :)
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo
On 16 Feb 2014, at 22:25 , Jeremy Lavergne wrote:
> You could reboot after each switch: anything that’s no longer linked into
> /opt/local won’t load, and everything else will launch the appropriate
> version.
Yes, that’s possible, but to "M$ Windows"-like! ;-)
There is still one big problem with all of this, which is that a ton of daemons
and agents might be running as root or as another user for a given MacPorts
installation.
In case I want to swap in another installation, say a debug installation, I
would have to make sure that all these services w
On 16 Feb 2014, at 21:46 , Jeremy Lavergne wrote:
> But I am assuming macports can handle being inside a symlink since I recall
> it can operate across drives.
Thanks, Jeremy.
That seems to be a good approach.
Greets,
Marko
___
macports-dev mailing l
Thanks, Sean!
On 16 Feb 2014, at 21:29 , Sean Mehta wrote:
> $ ./configure --prefix=$MP_PREFIX
> --with-applications-dir=$MP_PREFIX/Applications \
> --with-tclpackage=$MP_PREFIX/Library/Tcl
I knew that this trick would work, because I used that in the past with m
I just wanted to set up a 2nd parallel MacPorts install - as I used to have it
before moving to Mavericks…
Now I realise that it is probably not a good idea to have a setup like that
after all.
Some applications install themselves into /Applications and have settings in
/Library…
Assuming I h
Hi Clemens,
On 10 Feb 2014, at 12:01 , Clemens Lang wrote:
> You can just install trunk right over your old installation… Note that
> selfupdate will no longer do anything once you installed trunk. If you want
> to update your MacPorts installation you need to svn up your working copy of
> tru
Hi,
I would like to try MacPorts’ current trunk version.
How do I do this seamlessly, i.e. is it necessary to reinstall MacPorts from
scratch, or can I somehow manage to keep all installed ports in place while
just switching from my existing installation to trunk??
Greets,
Marko
__
On 09 Feb 2014, at 22:12 , Clemens Lang wrote:
> but it's really the port that's to blame here.
I see your point, but that’s probably something which might occur more often
than we think now, effectively making it impossible to find actually existing
ports. Probably it would make sense to handl
> The problem here is that the aqbanking Portfile violates lint:
Oh, good to know.
Can be fixed. :)
Will do so right away.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Hi Clemens,
I am seeing a page stating this:
—
The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.
—
in case I try to search for a non-existing or replaced_by port, e.g. [1].
I guess one could rather state on this page that the port is repl
On 09 Feb 2014, at 20:42 , Jeremy Lavergne wrote:
> You probably need to run trunk for access to POST, which isn’t available in a
> release yet.
Ooops, I see. I wasn’t aware of that trunk is a must for this feature.
___
macports-dev mailing list
macport
Hi Clemens,
I installed mpstats but when trying to submit my installation details I got
this error thrown:
—
$ /opt/local/libexec/mpstats submit
Submitting to http://stats.macports.neverpanic.de/submissions
Error: bad option "post": must be fetch, isnewer, or getsize
while executing
"curl pos
On 14 Jan 2014, at 03:02 , Ryan Schmidt wrote:
> Perhaps you could contribute to resolving the MacPorts VirtualBox ticket
> then.
I am afraid my knowledge about setting up a proper virtualbox installation is
not sufficient for this endeavour.
I tried a while ago though.
Ticket #41392 hangs aro
On 13 Jan 2014, at 09:54 , Rainer Müller wrote:
> You need -usb to activated USB support as it is not a default option. I
Oh, I wasn’t aware of that!
But well, this didn’t change anything with OpenSUSE 13.1…
> Yes, QEMU on Mac OS X is quite slow as it does not get any
> virtualization support.
…
On 12 Jan 2014, at 23:59 , Clemens Lang <> wrote:
> I've that a few times now and it seems to be a problem with permissions on
> the cache directory mentioned in the error message. Unfortunately it doesn't
> abort but it seems it can still lead to miscompiled code and performance
> degradation.
On 12 Jan 2014, at 22:41 , Chris Murphy wrote:
> Maybe. Try adding -usbdevice tablet to the qemu command line.
That made my trackpad almost unusable. :-(
But it didn’t change anything.
No progress during the system probe step.
___
macports-dev mailing
OK, now I found out using “info usb” that USB support is NOT enabled by default.
So, perhaps that is the problem?
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 12 Jan 2014, at 21:50 , Chris Murphy wrote:
> When I say USB device, I meant the interface in qemu that presents USB within
> the guest. Clearly the linux kernel is finding a USB bus.
The command line to start up the VM is
—
qemu-system-x86_64 -m 2G -cdrom openSUSE-13.1-NET-x86_64.iso -vga st
Hi devs,
I am trying to build some software using standard clang on Mavericks and I see
errors due to denied permissions like this:
—
:info:build libtool: compile: /usr/bin/clang -DHAVE_CONFIG_H
-DBUILDING_AQDATABASE -DLOCALEDIR=\"/opt/local/share/locale\"
-DAQDATABASE_PLUGINS=\"/opt/local/lib
On 12 Jan 2014, at 20:31 , Chris Murphy wrote:
> So I think you need to remove the USB device in the qemu guest and see if
> that works.
Chris, so far I am not trying to use any USB device. I am just trying to
install OpenSUSE using an ISO file…
Well, and the installation procedure is searchin
Hi Josh,
On 12 Jan 2014, at 19:47 , Joshua Root wrote:
> Well, it is going to be a lot slower than VirtualBox, as qemu is an
> emulator under these circumstances. Though there could also be issues
> with the USB support.
it’s an emulator, because it cannot make use of kvm...
>> P.S.: qemu likes t
I wanted to give qemu a shot - as an alternative for the currently
non-functioning virtual box [1] …
Anyone out there who’s successfully using qemu on Mavericks?
The small test linux image supplied by the qemu folks is running fine, but I am
stuck installing OpenSUSE 13.1...
Either qemu
On 31 Dec 2013, at 02:20 , Lawrence Velázquez wrote:
> In my (admittedly limited) experience, Launchpad updates itself based on the
> live contents of /Applications (and maybe ~/Applications, but I don't use
> that).
Perhaps I wasn’t patient enough and should have rebooted to make MacOSX’s
lau
Hi Craig,
On 30 Dec 2013, at 15:57 , Craig Treleaven wrote:
> Yes, that would be expected behaviour. MacPorts has no way of
> knowing that the link was created so it ends up pointing to a
> now-deleted file after an uninstall.
ah, okay. I wasn’t sure, that’s why I asked. I thought there were e
Hi Craig,
after deinstallation of mythtv-core.27 I realised on 10.9 that
Myth_Filldatabase and Myth_Frontend stay behind in one of LauchPad’s MacPorts
application folders although they are invalid links.
Is this normal behaviour or a glitch in the deinstallation phase?
Greets,
Marko
__
On 06 Dec 2013, at 10:20 , Ryan Schmidt wrote:
> The _mysql user is created by the mysql server ports. mysql5-server,
> mysql51-server, myqsl55-server, mysql56-server, mariadb-server,
> percona-server; pick whichever goes with the version of mysql you’re using.
Ah, okay. I should have just done
Hi Graig,
I successfully installed MythTV on my 10.9 last night.
Looking at the wiki hinted out in the port’s notes I notice that the described
initial MySQL setup fails for me already at
---
sudo -u _mysql mysql_install_db5
—
since there is no user _mysql on my system.
Would be great if you co
On 03 Dec 2013, at 23:18 , Ryan Schmidt wrote:
> All I can tell you is what cmake already told you: There is a circular
> dependency and it’s not allowed. Sounds like a broken cmake file. Have you
> reported this to whoever wrote it? They need to fix it.
I see, Ryan.
Thanks for responding.
:-)
G
Hi,
when trying to set up a new port I ran into a strange thing with cmake:
---
:info:configure -- Configuring done
:info:configure CMake Error: The inter-target dependency graph contains the
following strongly connected component (cycle):
:info:configure "server" of type SHARED_LIBRARY
:info:c
On 15 Nov 2013, at 18:32 , Shreeraj Karulkar wrote:
> We are very close, you should have a Mavericks buildbot by the EOD today.
You kept your promise, Shree! :)
Great stuff!!!
I have installed most of my MacPorts ports locally on my Maverick by last night.
All went surprisingly smooth, except th
Hi MacPorts core devs,
just now I once again missed a feature I wish was there in MP.
If I install a lot of ports (when I am setting up a machine from scratch, like
now) or upgrade an installation which hadn’t been upgraded for a longer time I
am overwhelmed by the amount of lines flooding my c
Hi Shree,
> We are very close, you should have a Mavericks buildbot by the EOD today.
by all accounts, that's just great news!
Thanks for your efforts.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforg
On Oct 23, 2013, at 6:12 PM, William Siegrist wrote:
> I just wanted to assure people that we are going to be working on adding a
> Mavericks and Linux (base-only) slave to build.macports.org. I’m not sure on
> the ETA, but I suspect we’ll have them done next week.
Hi Bill,
how is the progress
Thanks, Ryan.
I missed that.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
I have received responses like these from Mac OS Forges' mail server:
---
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error. The following address
failed:
"macports-dev@list
Hi Joshua,
I made it obsolete in r111928.
Greets,
Marko
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Oct 5, 2013, at 12:54 PM, Rainer Müller wrote:
> We have point 8. there, "Commit messages should make clear what has
> been changed":
Oh, I missed that one.
> I added a link to the new wiki page there as well.
I see.
> We could now probably remove the three points below that as they are cover
On Oct 4, 2013, at 8:41 PM, Joshua Root wrote:
> Why bump the revision when it fails to build either way? If this depends
> on a port that no longer exists, shouldn't it just be deleted? (If
> anyone has an older version of aqbanking installed, it will be
> automatically deactivated and replaced wi
I figured that a section about rules concerning properly formatted commit
messages are missing in the wiki (not to talk about the Guide), which is why I
created the following page:
https://trac.macports.org/wiki/CommitRules
below the committers guide
https://trac.macports.org/w
On Sep 26, 2013, at 12:32 AM, Ryan Schmidt wrote:
> The reason 3.2.6 is recommended and the default is because it is the last
> free version of Xcode for Snow Leopard.
Thanks for pointing this out, Ryan!
___
macports-dev mailing list
macports-dev@lists
Hi Chris,
On Sep 25, 2013, at 11:42 PM, Chris Jones wrote:
> Any guide that is telling you to manually start fiddling with sym links in
> system areas, is a guide you should stay away from.
That's what I also thought...
> Just a thought, but maybe updating to an Xcode 4 release, there is one for
1 - 100 of 241 matches
Mail list logo
