On 20/08/2016, at 11:51 PM, Ryan Schmidt wrote:
>
> On Aug 19, 2016, at 10:24 PM, Lawrence Velázquez wrote:
>
>> Any documentation we write should be written specifically for developers
>>
>> 1. who are accustomed to using Subversion, and
>> 2. want to translate *their MacPorts workfl
On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote:
>> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote:
>> As a KDE developer (and spectator of the changeover from svn to git) I have
>> found
>> this cheat sheet very useful, but not quite covering all situation
Hi Lawrence,
On 20/08/2016, at 1:24 PM, Lawrence Velázquez wrote:
>> On Aug 19, 2016, at 11:16 PM, Ian Wadham wrote:
>>
>> Qt and KDE moved from svn to git a while back. IIRC it was quite an effort
>> for a
>> few individuals to port all the repositori
On 20/08/2016, at 11:49 AM, Mark Anderson wrote:
> I use git (and Github Enterprise) in my day to day work. I can help out.
>
> Another good (free (as in beer)) client is SourceTree
> https://www.sourcetreeapp.com/
Qt and KDE moved from svn to git a while back. IIRC it was quite an effort fo
Hi René and Nicolas and everybody,
On 07/01/2016, at 1:44 AM, René J.V. Bertin wrote:
> I'm sure you've noticed that I'm making progress with ports for KF5.
Yep. Good on yer, René!
And it is nice to see that David Faure and other KDE core developers are taking
an interest at last...
> KF5 is
On 21/11/2015, at 7:15 AM, Bradley Giesbrecht wrote:
> Bam, confidence restored!
Congratulations, Ryan! It is great to know that you will be
the person handling this important job.
I hope you will still find some time to answer queries on the list
or that someone else will step into your shoes.
On 06/08/2015, at 4:14 AM, Kyle Sammons wrote:
> Hey everyone,
>
> Currently I'm at a fork in the road for the Revitalizing Pallet GSoC
> project, and was hoping to crowd source some ideas about how to deal
> with the Apple authorization framework used to get super user privileges
> to allow 'po
Hi Kyle,
On 02/06/2015, at 11:15 AM, Kyle Sammons wrote:
> Ian wrote:
> Well, Kyle, if you are interested, I could send you the code of Fossick and a
> specification/design document. You would be welcome to re-use any of it or
> any of the ideas contained in it
>
> Thanks for the offer, Ian! I'm
Hi Kyle,
On 07/05/2015, at 8:14 AM, Kyle Sammons wrote:
> My name's Kyle Sammons and I've been accepted into this years GSoC. I was
> also a GSoC participant for MacPorts last year working on Project "Clean-up
> Stuff", which created the "port doctor" and "port reclaim" commands.
I had been hop
Hi René,
Well, I think we really are (getting somewhere). Keep pushing! :-)
On 12/03/2015, at 5:44 AM, René J.V. Bertin wrote:
> Not that it's getting any easier to convince the powers that be what *I*
> think will be ideal for the QStandardPaths in port:qt5-mac, but at least I
> seem to have
On 12/02/2015, at 10:34 AM, Brandon Allbery wrote:
> On Wed, Feb 11, 2015 at 6:31 PM, René J.V. wrote:
> I take that to mean that doing fork() doesn't oblige you to do an exec()
> afterwards, it's that you cannot do a fork() from a process that's not been
> started through exec.
>
> I will gues
Hi guys,
I am the person who has this problem --- about 3 Gb of stuff in ~/.macports
and a Time Machine that goes berserk, running mtmd [1] at about 90% CPU
during "port clean" for example. I have had to turn Time Machine off.
On 10/02/2015, at 10:47 PM, Clemens Lang wrote:
> - On 10 Feb, 20
On 10/02/2015, at 9:37 PM, René J.V. Bertin wrote:
> On Tuesday February 10 2015 21:08:18 Ian Wadham wrote:
>
> Hi Ian,
>
> Taking this to macports-dev...
>
> As I said, my ~/.macports on my Mac appears to be unused since november 2013
> or so. However, the tiny t
On 12/01/2015, at 9:47 AM, René J.V. Bertin wrote:
> Ultimately you'll have /opt/local/libexec/qt4 and /opt/local/libexec/qt5 (and
> who knows, qt6 too).
> There really is no reason to worry. People on Linux have been going through
> those same
> motions for quite a while now.
OK. Thanks for cl
In case anyone does not already know, QTDIR is an env variable
a developer can use when developing software based on Qt or
a development (test, non-standard) version of Qt.
I always export QTDIR=/opt/local when I am developing or building
with a bleeding-edge version of KDE libraries, externally t
On 12/01/2015, at 8:30 AM, Brandon Allbery wrote:
> On Sun, Jan 11, 2015 at 4:28 PM, Clemens Lang wrote:
> - On 11 Jan, 2015, at 22:21, Ian Wadham iandw...@gmail.com wrote:
> > Is there a good reason why we have the yersinia port on MacPorts? Please
> > read the descripti
Hi guys,
Is there a good reason why we have the yersinia port on MacPorts? Please
read the description in full.
Best regards, Ian W.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports
Hi René,
On 09/01/2015, at 1:00 AM, René J.V. Bertin wrote:
> A remark about OS X not providing posix_fallocate led me to browse
> kshareddatacache_p.h (because posix_fallocate can be emulated), and therein I
> noticed
>
> #if defined(_POSIX_THREAD_PROCESS_SHARED) && ((_POSIX_THREAD_PROCESS_SHA
On 24/12/2014, at 9:27 PM, René J.V. Bertin wrote:
> On Wednesday December 24 2014 21:16:54 Ian Wadham wrote:
>> The code always seems to work OK if the crash procedure in the failed
>> program starts Dr Konqi by forking. But it never works (on Apple OS X)
>> if the crash
On 24/12/2014, at 8:52 AM, Joshua Root wrote:
> On 2014-12-24 08:15 , Ian Wadham wrote:
>> Hi Clemens,
>>
>> On 23/12/2014, at 11:33 PM, Clemens Lang wrote:
>>> - On 23 Dec, 2014, at 13:02, René J.V. Bertin rjvber...@gmail.com wrote:
>>>> IIRC,
Hi Clemens,
On 23/12/2014, at 11:33 PM, Clemens Lang wrote:
> - On 23 Dec, 2014, at 13:02, René J.V. Bertin rjvber...@gmail.com wrote:
>> IIRC, OS X no longer allows setuuid/setguuid, or only under some conditions.
>> Isn't that something that ought to be addressed in the post-destroot?
>> I'd
On 15/12/2014, at 9:46 AM, René J.V. Bertin wrote:
> 'evening!
>
> I finally got around to finishing up (or almost) my draft version for a
> qt4-mac port that can live alongside other (future) Qt port versions
> installed with the same approach: see https://trac.macports.org/ticket/46238 .
>
Hi guys,
On 19/11/2014, at 9:34 AM, Joshua Root wrote:
> On 2014-11-19 06:48 , Clemens Lang wrote:
>> I'd like to clean up the database schema of the registry. We have a couple
>> of fields in there that are currently unused, as well as a few possible
>> indices that could improve performance and
Hi Bradley,
On 05/11/2014, at 5:26 AM, Bradley Giesbrecht wrote:
> On Nov 3, 2014, at 6:10 AM, Andrea D'Amore wrote:
>> On Fri, Oct 31, 2014 at 9:01 PM, Ian Wadham wrote:
>>> On 01/11/2014, at 5:23 AM, Bradley Giesbrecht wrote:
>>>> A nice SQlite GUI app:
&g
On 01/11/2014, at 5:23 AM, Bradley Giesbrecht wrote:
> A nice SQlite GUI app:
> https://github.com/sqlitebrowser/sqlitebrowser/releases
Don't we already have sqlitedbrowser in MacPorts? Apart from
the "d", what is the difference?
Cheers, Ian W.
___
m
Hi Nicolas,
On 27/10/2014, at 3:02 PM, Nicolas Pavillon wrote:
> On 27/10/2014 12:24, Ian Wadham wrote:
>> Well, I just tried that and here is what happened…
>>
>> Tara:~>sudo port install palapeli +debug
>> ---> Computing dependencies for palapeli
>&
Hi again Ryan,
On 27/10/2014, at 2:24 PM, Ian Wadham wrote:
> On 27/10/2014, at 1:13 PM, Ryan Schmidt wrote:
>> On Oct 26, 2014, at 9:03 PM, Ian Wadham wrote:
>>> Variants in MacPorts are global in scope, which means that variants like
>>> "debug" and
Hi Ryan,
On 27/10/2014, at 1:13 PM, Ryan Schmidt wrote:
> On Oct 26, 2014, at 9:03 PM, Ian Wadham wrote:
>> On 27/10/2014, at 12:10 PM, Ryan Schmidt wrote:
>>> On Oct 26, 2014, at 7:10 PM, Marko Käning wrote:
>>>
>>>> Ryan, any suggestions?
>>>
Hi Ryan,
On 27/10/2014, at 12:10 PM, Ryan Schmidt wrote:
> On Oct 26, 2014, at 7:10 PM, Marko Käning wrote:
>
>> Ryan, any suggestions?
>
> My suggestions are:
>
> We try to avoid variant names beginning with "no". We try to use variant
> names that
> mention enabling something, rather than na
On 29/09/2014, at 3:25 PM, Nicolas Pavillon wrote:
> On 29/09/2014 13:03, Brandon Allbery wrote:
>> On Sun, Sep 28, 2014 at 11:51 PM, Brandon Allbery
>> wrote:
>> If I understood other discussions correctly, KDE3 is already being removed.
>>
>> Sorry, not discussions; recent commit messages ind
On 05/09/2014, at 10:20 AM, Lawrence Velázquez wrote:
> On Sep 4, 2014, at 8:04 PM, Ian Wadham wrote:
>
>> So why not "checkself"? Cheers, Ian W.
>
> Because it's not "updateself", it's "selfupdate".
Well, I was also going to suggest
On 05/09/2014, at 9:59 AM, Lawrence Velázquez wrote:
> On Sep 4, 2014, at 5:07 PM, Eric Gallager wrote:
>
>> Does it have to parallel "selfupdate"? "diagnose" works perfectly well
>> by itself without the "self" in front of it...
>
> Of course it doesn't *have* to. But most of the port(1) verb
Hi David and Marko,
On 23/08/2014, at 8:37 AM, David Evans wrote:
> On 8/22/14 12:41 PM, Marko Käning wrote:
>> how can I determine the dbus address of the session dbus started by launchd?
>>
>> The environment contains only DBUS_LAUNCHD_SESSION_BUS_SOCKET:
>> —
>> DBUS_LAUNCHD_SESSION_BUS_SOCKET
On 15/07/2014, at 10:56 AM, Mark Brethen wrote:
> On Jul 14, 2014, at 6:22 PM, Mark Brethen wrote:
>
>> I'm testing the FreeCAD build and discovered that the help menu returns the
>> error message: "Unable to launch Qt Assistant
>> (/opt/local/bin/Assistant.app/Contents/MacOS/Assistant)". Laun
On 29/06/2014, at 7:52 PM, Marko Käning wrote:
> on the kde-mac ML the question came up whether the necessity to install
> qt4-mac in its
> debug variant - when one simply needs KDE ports installed in their debug
> variant - is only
> due to MacPorts' way of handling port variants...
>
> If that
On 16/06/2014, at 4:15 PM, Clemens Lang wrote:
> On June 16, 2014 5:57:36 AM CEST, Ian Wadham wrote:
>> On 16/06/2014, at 1:38 PM, Brandon Allbery wrote:
>>> The normal time you need such code is after a fork() and before
>> exec() to avoid leaking file descriptors to
On 16/06/2014, at 1:38 PM, Brandon Allbery wrote:
> On Sun, Jun 15, 2014 at 8:15 PM, Ian Wadham wrote:
> Later the the FDs get closed anyway and it works then, perhaps because
> the app gets issued with a STOP.
>
> Unix closes all fd-s at process exit (including abnormal exit) any
On 15/06/2014, at 6:28 PM, Clemens Lang wrote:
>>> On Sat, Jun 14, 2014 at 10:25 PM, Ian Wadham wrote:
>>> The procedure for closing the file descriptors is a bit brute force. It
>>> uses "struct rlimit rlp; getrlimit(RLIMIT_NOFILE, &rlp);" to fin
Thanks for your very prompt reply, Bradley.
On 15/06/2014, at 1:03 PM, Brandon Allbery wrote:
> On Sat, Jun 14, 2014 at 10:25 PM, Ian Wadham wrote:
> The procedure for closing the file descriptors is a bit brute force. It uses
> "struct rlimit rlp; getrlimit(RLIMIT_NOFILE, &
Hi guys,
I think I have found the reason for two KDE problems on OS X and MacPorts:
1. When a KDE app crashes, Dr Konqi often fails to run and produce
the backtrace KDE developers ask for.
2. Also the debug dialog fails to run and take the user through the
steps to report
Hello MacPorts Developers,
As you may know, I am a developer of KDE Games working on Apple OS X
Lion with an early-2011 Macbook Pro. I am here on a kind of diplomatic
mission from KDE-land. But first a few words of background.
KDE SC 4.13 is due for release on 16 April. Just over a month ago,
Hi guys,
The KDE build-system developers have now fixed the problem with
excessive symbol visibility (or invisibility in some cases), when Clang
is used to compile KDE.
The KDE build system, as of KDE 4.11.1, will have a section that recognises
Clang and creates appropriate settings. Technical d
It looks as though a solution to a problem compiling KDE with Clang
is near. Apparently BSD has now changed over to Clang and found
a similar problem, see https://bugs.kde.org/show_bug.cgi?id=313763
My original report was https://bugs.kde.org/show_bug.cgi?id=300429
KDE compiles and builds OK wit
On 06/06/2013, at 9:02 AM, Lawrence Velázquez wrote:
> On Jun 5, 2013, at 12:03 PM, Nicolas Pavillon wrote:
>
>> This error seem to appear because Qt forward-declares
>> random_access_iterator_tag in qiterator.h in the part:
>> #ifdef QT_NO_STL
>> namespace std {
>>struct bidirectional_ite
On 21/04/2013, at 12:51 AM, Jeremy Lavergne wrote:
>>> I am thinking of putting the tarball on Dropbox. Would that be suitable
>>> for list members to extract and review?
>> I've never used dropbox, but I guess anonymous access should be possible
>> there, right?
>
> Yes, Dropbox should be fin
On 21/04/2013, at 7:34 AM, Leo Singer wrote:
> On Apr 20, 2013, at 12:00 PM, macports-dev-requ...@lists.macosforge.org wrote:
>
>> From: Ian Wadham
>> Subject: Please review first draft of Fossick - a MacPorts GUI
>> Date: April 20, 2013 1:54:42 AM PDT
>> To: &quo
On 21/04/2013, at 11:49 AM, Ryan Schmidt wrote:
> On Apr 20, 2013, at 20:09, Ian Wadham wrote:
>
>> Fossick is looking for the "port" command in /opt/local/bin and the Index
>> file in
>> /opt/local/var/macports/sources/rsync.macports.org/release/tarba
On 21/04/2013, at 9:43 AM, Ryan Schmidt wrote:
> On Apr 20, 2013, at 18:17, Ian Wadham wrote:
>> On 21/04/2013, at 7:33 AM, Ryan Schmidt wrote:
>>> All three panes are empty; I can't figure out how to make it do anything.
>>
>> I am sorry to hear that.
>
Hello Kevin,
On 21/04/2013, at 4:28 AM, Kevin Walzer wrote:
> I'm the competition here (http://www.codebykevin.com/portauthority.html), but
> since no one else has provided any comments yet, I'll offer a few.
Thank you for being so chivalrous as to review my code.
> The app felt very sluggish t
On 21/04/2013, at 7:33 AM, Ryan Schmidt wrote:
> On Apr 20, 2013, at 03:54, Ian Wadham wrote:
>
>> b. The GUI - how it works, ease of use, etc.
>
> All three panes are empty; I can't figure out how to make it do anything.
I am sorry to hear that.
It probably means
Hi guys,
The first draft of the MacPorts GUI app called Fossick can be downloaded from:
http://www.filedropper.com/fossickclonetar
by clicking a Download button or two, once you can find your way past all the
ads. Does anybody know a better file share site? I'm a newbie at this stuff.
If
On 18/04/2013, at 5:42 AM, mk-macpo...@techno.ms wrote:
> if you haven't commit access to MacPorts' SVN server you could use github or
> bitbucket to publish your code.
Thanks, Marko. I don't think I am ready to go remote with Fossick in git.
Amongst other reasons, I do not wish to risk messing
Hi guys,
The first draft of the Macports GUI (Fossick) is nearly ready for its
first push to a central repository.
So far, it can retrieve an index of all ports, search it in a couple of
ways, display information about a selected port (port info, port-file,
file content list and dependencies), di
Hi guys,
Attached is a pure-text file (made with vi), containing my ideas so far
for a new MacPorts GUI. Comments, suggestions and reviews are
welcome.
It is intended to be a simple tool for first-time users (in Basic mode)
and a more versatile tool for more advanced users (in Advanced
mode) to
On 13/03/2013, at 11:07 AM, Nicolas Pavillon wrote:
> That's interesting, because there was a discussion some days ago about
> keeping (or not) kde3 in macports after its deprecation. I did not try to
> install kdelibs3 for a long time (essentially due to the conflict with kde4),
> though. The
On 07/03/2013, at 7:03 PM, mk-macpo...@techno.ms wrote:
> On Mar 7, 2013, at 4:57 AM, Ian Wadham wrote:
>> I looked at the main.log for ticket 37620, but there is a lot of concurrency
>> and it is hard…
> Concurrency?! I wasn't aware of that, actually.
You must be. &qu
Hello Marko,
On 06/03/2013, at 9:00 AM, mk-macpo...@techno.ms wrote:
> On Mar 5, 2013, at 10:47 PM, Ian Wadham wrote:
>> On 06/03/2013, at 1:14 AM, Jeremy Lavergne wrote:
>>> * doc building used meinproc4, which routinely crashed and prevented
>>> installatio
On 06/03/2013, at 10:15 AM, Lawrence Velázquez wrote:
> On Mar 5, 2013, at 4:47 PM, Ian Wadham wrote:
>
>> My reasons for discontinuing the +docs variant in KDE ports would be:
>>
>> - It brings in additional dependencies needed by Doxygen but not by all
>>
On 06/03/2013, at 1:27 AM, Nicolas Pavillon wrote:
>> 1. Do we need the kde-i18n- ports?
>
> As these ports are from the kde3 suite, I would say they are as relevant as
> any KDE 3 port.
Understood.
>> 2. Do we need the KDE 3 ports?
>
>
> It seems there is indeed not much left which uses kde
the best, Ian W.
> On Mar 5, 2013, at 12:01 AM, Ian Wadham wrote:
>
>> 4. Many KDE apps come with user manuals: should MacPorts install them by
>> default?
>>
>> If no, I will add a recommendation to the Wiki to use the +docs variant.
>> If yes,
>>
On 06/03/2013, at 12:14 AM, Nicolas Pavillon wrote:
> I wrote it a certain way to try to emphasize the necessity of performing
> these steps, even though it may not have been the best choice of words. I
> corrected it to hopefully avoid confusion.
Fine by me.
Nicolas, are you happy overall wi
Hi guys,
For as long as I can remember (well, back to Macintosh days anyway),
I have been going into Apple dealers, including the current chain of
Apple Stores, and seeing customers (including me) asking for office
apps and being told to buy Microsoft Office for Apple.
This is surely a regrettabl
On 03/03/2013, at 4:28 PM, Lawrence Velázquez wrote:
> On Mar 3, 2013, at 12:05 AM, Ian Wadham wrote:
>
>> This page is an excellent start, Nicolas!
>>
>> I have one or two points to add to it. Where do I find the wiki source? Can
>> I edit it? Probably not.
On 05/03/2013, at 12:22 PM, Jeremy Lavergne wrote:
>> Unfortunately, MacPorts **does not provide an out-of-the-box working
>> installation**.
>
> I'd almost leave that sentence out, and stick with the general "these are the
> steps for doing ... in MacPorts".
Those were Nicolas' original words
On 03/03/2013, at 4:28 PM, Lawrence Velázquez wrote:
> On Mar 3, 2013, at 12:05 AM, Ian Wadham wrote:
>
>> This page is an excellent start, Nicolas!
>>
>> I have one or two points to add to it. Where do I find the wiki source? Can
>> I edit it? Probably not.
On 03/03/2013, at 1:40 AM, Nicolas Pavillon wrote:
> I created a page (https://trac.macports.org/wiki/KDE) with the information I
> thought relevant for now, and added its link to the main wiki page.
> As I do not consider myself a KDE expert neither a Macports one, some parts
> may be incomplet
On 02/03/2013, at 6:25 PM, Ryan Schmidt wrote:
> On Mar 2, 2013, at 01:23, Nicolas Pavillon wrote:
>> Following the discussion concerning the improvement of the display of port
>> notes, I was also considering gathering the information for installing KDE
>> ports somewhere. I noticed that while w
On 20/02/2013, at 11:43 AM, Jordan Hubbard wrote:
> On Feb 14, 2013, at 12:46 AM, Rainer Müller wrote:
>> The message classification currently happens through a handful of procs
>> such as ui_error, ui_warn, ui_msg, ui_notice, ui_info, ui_debug. These
>> add the prefix for errors and warnings and
Hi guys,
Here is something you might like to have a look at.
On 10 Feb, Guido Soranzio posted here
https://lists.macosforge.org/pipermail/macports-dev/2013-February/021976.html
about his new Guigna app. You can find it on GitHub at:
https://github.com/gui-dos/Guigna
and you can clone it (ch
On 13/02/2013, at 12:06 PM, Jordan Hubbard wrote:
> On Feb 10, 2013, at 8:13 PM, Ian Wadham wrote:
>
>> I heartily agree with you that "wrapping basic commands" is not enough.
>> I particularly hate GUIs that wrap basic programming and then pass
>> through bas
ts GUI,
> which will hopefully explain the state of the project.
>
> On 2013-02-10 10:59, Ian Wadham wrote:
>>
>> On 10/02/2013, at 8:11 PM, Ryan Schmidt wrote:
>>> On Feb 10, 2013, at 00:39, Ian Wadham wrote:
>>>> Should I persevere with Macports_Fra
On 12/02/2013, at 9:03 PM, Rainer Müller wrote:
> On 2013-02-12 05:29, Guido Soranzio wrote:
>> On 11/02/2013, Ian Wadham wrote:
>>> I see that Cocoa has NSTask and NSPipe classes and that Guido's
>>> Guigna app is using them in its GuignaAgent class. I also lik
On 11/02/2013, at 4:51 AM, Kevin Walzer wrote:
> On 2/10/13 1:39 AM, Ian Wadham wrote:
>> Should I persevere with Macports_Framework? It's been a while since I
>> worked with threads and concurrent processes and Apple's way of doing
>> things, in Objective C, OS X
Hello Guido,
On 10/02/2013, at 10:36 PM, Guido Soranzio wrote:
> On 10/02/2013, Ian Wadham wrote:
>> Maybe there is scope for a simpler interface to Macports, such as
>> running scripts and intercepting the output, but I have not looked at
>> that.
>
> You can ha
On 10/02/2013, at 8:11 PM, Ryan Schmidt wrote:
> On Feb 10, 2013, at 00:39, Ian Wadham wrote:
>> Should I persevere with Macports_Framework?
>
> What alternative do you propose?
For myself, acting alone? None. Find something smaller and
easier to work on - not Macports_Frame
Hello everybody,
I raised this topic on macports-users under the subject "How to
get a full list of dependents?", but it is undoubtedly better to
discuss it here and under a proper subject line.
I have been studying the source code of Pallet and
Macports_Framework and doing a bit of testing of bo
76 matches
Mail list logo
