Re: GSoC 2014 - Interactive Port Command and
Hi Marcus, On Tue, Feb 25, 2014 at 11:18:27PM +, Marcus Santos wrote: I already started to read the Tcl tutorial on GSoC’s page and I would be grateful if you can help me to learn more about the project. The Tcl tutorial is certainly a good start, as is learning a little about Portfiles and how they work from https://guide.macports.org. Regarding the interactive port command proposal: There currently are some places in MacPorts where a user action is aborted because of a conflict that needs to be resolved manually. Since there is no API to communicate with a user (and ask for decisions or approval), MacPorts usually just errors out in these cases, printing some instructions on what to do next. To understand why this is a problem (and the code that does that can't just print a message and wait for user input directly) you need to be aware of some of MacPorts' architectural principles: The port(1) command you actually use when giving MacPorts commands is just a frontend for the macports1.0 package, which really is the core of MacPorts. This package knows about Portfile, where they are and how they need to be run; it creates Tcl slave interpreters, resolves dependencies, runs Portfiles, etc. Another vital part is the API offered to Portfiles (i.e. all the commands that can be used from a Portfile), which is contained in the port1.0 package. In theory (that hasn't happened so far), port(1) is only *one* possible client for MacPorts. All interaction between port(1) and macports1.0 should also be possible from a MacPorts GUI for example (note that there are some GUIs available, but to my knowledge none of them works using that principle). Your job would thus be to draft and implement an API extension for the interface offered by the macports1.0 package to allow asking the user questions and waiting for user feedback, possibly using a series of callback functions. The recently added progress bars [1] might give you an impression how that can be done. Your job would also be to identify places where interactivity would make sense and implement it there. Three examples come to mind immediately: - When trying to install a port that conflicts with a port you already have installed, ask the user whether the conflicting port should be disabled. - When trying to install a port but one of the files installed by this port is already present, ask the user whether the file should be overwritten. - When a user tries to install a port, display a list of ports that will be installed as dependencies and ask for confirmation (unless there aren't any dependencies to be installed), like apt-get does. Keep in mind that for non-interactive invocations (i.e. port(1) running without being connected to a TTY) should still work just like before. If you have any further questions, feel free to ask right away -- after all communication is pretty much half of what GSoC is about :) [1] http://trac.macports.org/changeset/117044 http://trac.macports.org/changeset/117045 http://trac.macports.org/changeset/117046 http://trac.macports.org/changeset/117186 http://trac.macports.org/changeset/117219 http://trac.macports.org/changeset/117231 -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Getting Introduced with the Community and Looking forward to Contribute to the Project as part of Gsoc 2014
Hi Gaurav, On Thu, Feb 27, 2014 at 03:21:56AM +0530, Gaurav Bansal wrote: GNU C/C++, Python, Java,PHP/MySQL Version control systems and Git/Github Do you know any Tcl? Are you willing to learn? Working for MacPorts without Tcl knowledge isn't going to get you very far. I had installed the required necessary tools and setup the environment in my system needed for the contribution to open source software. I had got myself aware of the source to some extent. I had also read the contribution, development tutorial on the community webpage. So you actually already checked out the source code? Do you have any questions on that? Anything unclear where we could help you? I would like to seek the mentors help in the selection of the project for which the idea has been proposed for the Gsoc and someone is willing to mentor the project idea. I assume you have already read our ideas page at https://trac.macports.org/wiki/SummerOfCode? Is there anything on that list that you're interested in particularly? I will highly appreciate with any kind of help, guidance from the mentors to help me move forward to contribute to the software starting off with some easy tasks and then moving levels higher so as to make a strong proposal for the upcoming Google Summer of Code 2014. Forgive me for being blunt, but did you copy most of the text in this mail from other students' application emails? I've found at least three other emails using similar text with different names sent to other organizations' mailing lists: - http://plone.293351.n2.nabble.com/Getting-Introduced-with-the-Community-and-Looking-forward-to-Contribute-to-the-Project-as-part-of-Gs4-td7570054.html - http://comments.gmane.org/gmane.comp.python.devel/145461 - https://groups.google.com/forum/#!msg/sympy/K7qNXgdlQIg/EW5pRhaZhR4J -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
#42468: py-scipy @0.13.3: enable py34 subport
Hi Sean and Michael, Have you had the occasion to look at ticket #42468: py-scipy @0.13.3: enable py34 subport, python34 @3.4.0rc1 ? http://trac.macports.org/ticket/42468 Is there any particular problem involved with implementing this? ~petr smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: An introduction from a hopeful GSOC participant
Hi Kyle, On Thu, Feb 27, 2014 at 04:17:38PM -0800, Kyle Sammons wrote: Sorry to be a bit tardy-to-the-GSOC-party, but it got pretty busy up here this week. Anywho, I read on the wiki that it'd probably be a good idea to introduce myself here, so I figured I'd give it a shot. Don't worry, you're not too late -- there's still a lot of time until the applications are due. Unfortunately, I haven't personally used the program, as a friend convinced me to use homebrew at the last second. However, when I saw that this was a GSOC project for this year, I just had to jump at the opportunity. Well, welcome to the dark side that's going to drive you to drink, then. Feel free to try whether this claim holds true for your experience with MacPorts and us. ;) I've looked over the list of ideas and came up with an idea for a project that is a bit of a hodgepodge of ideas from the wiki that all seemed like they'd go well together, with a bit of my own spin on it. I'm hoping to talk it over with a mentor, or someone who's more knowledgeable about this than me, so I can really solidify this plan before I officially submit it. Sure, you can reply to the mailing list, if you want; if you'd rather keep your proposal private at this point, you can reply to the others I've cc'd on this mail and me. I'm sure we can give you some feedback on your ideas and answer any questions you might have. Alrighty, I believe that should cover it all. I'll make sure to hop onto IRC soon (though I've already informally introduced myself there), and hopefully I'll see some of you there! :) You definitely will, yes. https://trac.macports.org/wiki/MacPortsDevelopers has a mapping from MacPorts handle to IRC nicks, if any, because that can sometimes be a little surprising. Looking forward to hearing from you :) -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Getting Introduced with the Community and Looking forward to Contribute to the Project as part of Gsoc 2014
Hello Clemens, Do you know any Tcl? Are you willing to learn? Working for MacPorts without Tcl knowledge isn't going to get you very far. I've almost done with the Tcl tutorial i.e. the given link for the tutorial on the Development page. Hoping that would be fine for moving further ahead with the code? Please suggest if something will help more. So you actually already checked out the source code? Do you have any questions on that? Anything unclear where we could help you? I've just got a basic gist of the code but still a lot left to explore. I am still going through the developers guide to cover as many aspects as possible. I assume you have already read our ideas page at https://trac.macports.org/wiki/SummerOfCode? Is there anything on that list that you're interested in particularly? I am particularly interested in the project titled as *Read packages from Python's PIP (pip2port)* Jeremy and Sterling were very helpful and earlier replied to my mail regarding the same on the mailing list. I'm still trying to get the hang of Portfile development using the developers guide. It'll be very helpful if you could just elaborate a bit more on the project and direct me in the right direction for a positive outcome. Forgive me for being blunt, but did you copy most of the text in this mail from other students' application emails? I've found at least three other emails using similar text with different names sent to other organizations' mailing lists: - http://plone.293351.n2.nabble.com/Getting-Introduced-with-the-Community-and-Looking-forward-to-Contribute-to-the-Project-as-part-of-Gs4-td7570054.html - http://comments.gmane.org/gmane.comp.python.devel/145461 - https://groups.google.com/forum/#!msg/sympy/K7qNXgdlQIg/EW5pRhaZhR4J I'm sorry for copying the text. It was my very first venture to the open source world and didn't wanted to mess it up.. Now knowing that what I did was very much stupid ...I'll make sure that a thing of such sort doesn't happen in future. Gaurav ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
MacPorts has been accepted into GSoC 2014
Hi, as you have probably noticed from the list traffic by now, MacPorts has been accepted into Google Summer of Code 2014 (10th anniversary edition!). Google will pay students to work for Open Source projects, which gives us the opportunity to get new features implemented. If you're a student in higher education or know somebody who is and would be interested in working with MacPorts this summer, take a look at our ideas page [1]. We're also looking for additional ideas and more mentors to help out with this year's batch of students, especially since I will be busy with my master's thesis during the first half of the program this year. If you have a little time every week during the summer and know your way around some of the base code or Portfile development you can help out. I'd also like to ask all potential mentors to register in Google's GSoC management tool Google Melange [2]. [1] https://trac.macports.org/wiki/SummerOfCode [2] http://www.google-melange.com/gsoc/homepage/google/gsoc2014 -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Editing www/index.php Not Going to Site?
I made an edit to the www/index.php, but it doesn’t seem to have deployed. Is immediate deployment expected? I’ve got an email ready to send to the admins if this is unexpected behavior. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
That can get bypassed for GSOC students though, right? At least that was how I remember mariusc got his commit rights, and he was the most recent committer added that I can think of... Anyways, with all these GSOC students that look like they are applying this year, perhaps when they get their commit rights, that could be used as an opportunity for the project managers to add some other people who have been waiting in line outside of the whole GSOC process as well? On Fri, Feb 21, 2014 at 10:05 PM, Lawrence Velázquez lar...@macports.org wrote: On Feb 21, 2014, at 11:53 AM, Peter Danecek peter.dane...@bo.ingv.it wrote: But maybe having more committers might reduce backlog, just a thought ... Membership requests are evaluated by the project managers only (Josh, Rainer, and Ryan). vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
Hi, That can get bypassed for GSOC students though, right? At least that was how I remember mariusc got his commit rights, and he was the most recent committer added that I can think of... The actual confirmation email still came from one of portmgr@, I think it was Rainer. So, no, this doesn't get bypassed for GSoC students either, but they're not subject to the process as the rest of us (or rather, you) are. Anyways, with all these GSOC students that look like they are applying this year, perhaps when they get their commit rights, that could be used as an opportunity for the project managers to add some other people who have been waiting in line outside of the whole GSOC process as well? IMO, now is as good a time as any. Why delay it if it's finished earlier? Of course portmgr@ are all volunteers, too. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
portmgr@ could grow to include another volunteer though :-P Maybe it should include someone as influential as Clemens. On Feb 28, 2014, at 15:42, Clemens Lang c...@macports.org wrote: IMO, now is as good a time as any. Why delay it if it's finished earlier? Of course portmgr@ are all volunteers, too. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
+1 Good choice. Regards, Bradley Giesbrecht (pixilla) On Feb 28, 2014, at 12:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: portmgr@ could grow to include another volunteer though :-P Maybe it should include someone as influential as Clemens. On Feb 28, 2014, at 15:42, Clemens Lang c...@macports.org wrote: IMO, now is as good a time as any. Why delay it if it's finished earlier? Of course portmgr@ are all volunteers, too. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
I agree that normatively, now would be better than later, I was just speculating descriptively about what it might take to get some new approvals... On Fri, Feb 28, 2014 at 3:42 PM, Clemens Lang c...@macports.org wrote: Hi, That can get bypassed for GSOC students though, right? At least that was how I remember mariusc got his commit rights, and he was the most recent committer added that I can think of... The actual confirmation email still came from one of portmgr@, I think it was Rainer. So, no, this doesn't get bypassed for GSoC students either, but they're not subject to the process as the rest of us (or rather, you) are. Anyways, with all these GSOC students that look like they are applying this year, perhaps when they get their commit rights, that could be used as an opportunity for the project managers to add some other people who have been waiting in line outside of the whole GSOC process as well? IMO, now is as good a time as any. Why delay it if it's finished earlier? Of course portmgr@ are all volunteers, too. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
Hey, portmgr@ could grow to include another volunteer though :-P Maybe it should include someone as influential as Clemens. As far as I know there actually is a process for that – I doubt these things work that way, but thanks for the trust :P -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: commit rights ...
+2 for Clemens being part of portmgr. Objectively, he would be a good choice due to his activity level and amount of contributions to the project. Biasedly, I would want him to be part of it because he was the one who encouraged me to apply for commit rights in the first place... On 2/28/14, Bradley Giesbrecht pixi...@macports.org wrote: +1 Good choice. Regards, Bradley Giesbrecht (pixilla) On Feb 28, 2014, at 12:56 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: portmgr@ could grow to include another volunteer though :-P Maybe it should include someone as influential as Clemens. On Feb 28, 2014, at 15:42, Clemens Lang c...@macports.org wrote: IMO, now is as good a time as any. Why delay it if it's finished earlier? Of course portmgr@ are all volunteers, too. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Editing www/index.php Not Going to Site?
On Feb 28, 2014, at 09:54, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: I made an edit to the www/index.php, but it doesn’t seem to have deployed. Is immediate deployment expected? I’ve got an email ready to send to the admins if this is unexpected behavior. Last I checked, yes, edits to the web site should be propagated to the live site automatically. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [117355] trunk/dports/sysutils/cardpeek/Portfile
On Feb 23, 2014, at 14:56, c...@macports.org wrote: Revision 117355 Author c...@macports.org Date 2014-02-23 12:56:10 -0800 (Sun, 23 Feb 2014) Log Message cardpeek: GPL is version 3 only, OpenSSL exception is granted Modified Paths • trunk/dports/sysutils/cardpeek/Portfile The files I saw said GPL 3 or newer. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
