February 2008 - macports-dev - lists.macosforge.org

Google SoC 2008
by James Berry 12 Mar '08

12 Mar '08

I'm writing to attempt to gauge interest in whether and how MacPorts should participate in Google Summer of Code (GSoC) for 2008. See http://code.google.com/soc/2008/ . You might be inclined to address any of the following questions: - Do you feel MacPorts should participate in GSoC 2008? - Are there particular MacPorts projects you'd like to suggest? - Are you willing to be a GSoC mentor? - Would you be interested, as a student, in participating in a GSoC project for MacPorts? GSoC pays students a wage for the summer to work on open source projects, and also a stipend to the project for each student project. If interested, we need to move very quickly. As the Google GSoC FAQ says: "We'll begin accepting applications from open source mentoring organizations on Monday, March 3, 2008; we'll stop accepting organization applications on Wednesday, March 12th." Your feedback is welcome James

8 20

Splitting the guide
by markd＠macports.org 10 Mar '08

10 Mar '08

> Hey guys! > > The guide is advancing so nicely that I'm afraid we've hit the >point >when it's maybe becoming a tad too large for a single page, wouldn't >y'all think? > > Every time I have to load a section of the guide a have a moment >of >hesitation in fear of loading such a large document! At this point in >time, wouldn't it be better to have a single html page per chapter? > > Just my thoughts,... > > >-jmpp Juan, Well I agree it is really too big, but on the other hand we hated to split it and have cumbersome "forward" and "back" buttons. Also it makes searching easier in one page, but then I suppose indexing might solve that. But then maybe a page for each chapter wouldn't be too bad. I guess we should experiment and see how it looks and drives. Mark

7 16

livecheck not finding latest version
by Adam Mercer 09 Mar '08

09 Mar '08

Hi I'm trying to get livecheck working for all my ports and am running into a strange problem for bzr-rebase. I have the following in the Portfile: livecheck.check regex livecheck.url ${master_sites} livecheck.regex ${name}-(\[0-9\]+\.\[0-9\]+).tar.gz the specified ${master_sites} points to the download location (http://samba.org/~jelmer/bzr) whenever I run livecheck I get the following displayed [ram@skymoo bzr-rebase]$ sudo port livecheck bzr-rebase seems to have been updated (port version: 0.3, new version: 0.2) [ram@skymoo bzr-rebase]$ Any ideas why livecheck is saying that 0.2 is newer than the ports 0.3, and how I can fix this? Is there a problem with my regular expression? Cheers Adam

4 5

py-twistedweb2 and py25-twisted-web2 uses different name convension
by js 08 Mar '08

08 Mar '08

Hi, I noticed that twisted for python2.4 and 2.5 uses different name convension. I opened new ticket http://trac.macosforge.org/projects/macports/ticket/14375 Shouldn' they use the same convension?

3 6

Fwd: [MacPorts] #14342: python25 drops modules by default, but python25 doesn't
by js 07 Mar '08

07 Mar '08

# Moving from Trac ticket #14342 > No, py25-foo can have different dependencies than py-foo. I don't know > what you wanted to tell us with this. I meant if we would change python24 to drop some standard modules like the current python25 port does, py-foo and py25-foo's dependencies would be the same. Not sure this is 100% same but almost the same I assume. > And there is no problem that we have more py-* ports than py25-* ports. We > just add what people request. If nobody needs a port, but it is in the > tree, it is just more work for maintainers. So if you need some port, ask > for it. No problem, but Python project now recommend users to use python2.5, not 2.4. Providing a lot of ports to python25 users would encourage users to use python2.5. Some people don't bother to write reports even if they want. I like to add more py25- ports to make python25 looks more *atrractive*. Forwarded Conversation Subject: [MacPorts] #14342: python25 drops modules by default, but python25 doesn't ------------------------ From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 11:51 AM #14342: python25 drops modules by default, but python25 doesn't -------------------------------+-------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: python | -------------------------------+-------------------------------------------- Python2.5 disables common modules by default, but python2.4 doesn't. See dports/lang/python25/files/patch-setup.py {{{ # This global variable is used to hold the list of modules to be disabled. -disabled_module_list = [] +disabled_module_list = ["zlib","_hashlib","_ssl","_bsddb","_sqlite3","_tkinter","bz2","gdbm","readline","_curses","_curses_panel"] }}} IMHO, all python pors should be as similar as they can be. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342> MacPorts </projects/macports> Ports system for Mac OS -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 11:52 AM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) If there's a reason, please make it clear by leaving comments about that on the patch file. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:1> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:02 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) These are provided as seperate ports. For example py25-hashlib, py25-zlib and others. I don't know what the advantage of that was, but we already had that discussion once. Portfile writers should include correct dependencies. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:2> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:18 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) I think that's OK, but the thing is python24 doesn't drop these modules. It's a weird... -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:3> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 12:44 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) If we were going to change this, it would require to change dependencies in nearly all py-* ports. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:4> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 1:59 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) Replying to [comment:4 raimue(a)macports.org] > If we were going to change this, it would require to change dependencies in nearly all py-* ports. Yes, we probably have to check py-ports that was not in py25 ports {{{ $ port list |egrep -i '^py-' | cut -d" " -f1 | sort -u > py24 $ port list |egrep -i '^py25-' | cut -d" " -f1 | sed 's/^py25/py/' | sort -u > py25 $ wc -l py2[45] 338 py24 109 py25 447 total $ comm -2 -3 py24 py25 > py24-only $ wc -l py24-only 259 py24-only }}} How about create py25- ports of all 259 py24 only ports? To create py25-ports, we need to know the port need zlib or hashlib, which helps identify this py24 ports should be fixed. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:5> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 6:27 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by ebgssth(a)gmail.com) From a different point of view, that MacPorts has lots more python2.4 ports than python2.5's seems weird to me. (Python 2.5 is the current stable, Python 2.4 series will be no longer released anymore) Should I open another ticket about this problem? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:6> [Quoted text hidden] -------- From: MacPorts <trac(a)macosforge.org> Reply-To: noreply(a)macosforge.org To: ebgssth(a)gmail.com, macports-tickets(a)lists.macosforge.org Cc: mww(a)macports.org Date: Sat, Feb 16, 2008 at 9:33 PM #14342: python25 drops modules by default, but python25 doesn't --------------------------------+------------------------------------------- Reporter: ebgssth(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Resolution: | Keywords: python --------------------------------+------------------------------------------- Comment (by raimue(a)macports.org) Replying to [comment:5 ebgssth(a)gmail.com] > Yes, we probably have to check py-ports that was not in py25 ports No, py25-foo can have different dependencies than py-foo. I don't know what you wanted to tell us with this. And there is no problem that we have more py-* ports than py25-* ports. We just add what people request. If nobody needs a port, but it is in the tree, it is just more work for maintainers. So if you need some port, ask for it. PS: This kind of discussion would have been better on the mailing list. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14342#comment:7> [Quoted text hidden] --------

4 9

New HOWTO section in the wiki
by Rainer Müller 06 Mar '08

06 Mar '08

Hi, I started a new HOWTO section in the wiki [1]. These HOWTOs should cover tutorials and tips how specific things can be done using MacPorts. This is meant to be an addition to the guide and should not contain topics already covered by the guide. It is a place editable by everyone to share tips and tricks. So far I just added two HOWTOs to demonstrate how they should look like. If you have a good idea what such a HOWTO could cover, feel free to add it to the list. And if you even want to help by writing a HOWTO/tutorial yourself in order to make using MacPorts easier, there is a template which you can use as a start. So far I added two HOWTOs, one explaining how to use ccache and another how parallel building can be enabled. Of course you are free to edit them e.g. to add further information. Also, there is a list what could also be written. Even if you don't have time to write a HOWTO yourself, please make your mind what else could be useful and add it to that list. Rainer [1] http://trac.macosforge.org/projects/macports/wiki/howto

2 2

user instructions - was ... mysql5 + php5 + apache2
by markd＠macports.org 29 Feb '08

29 Feb '08

>> I don't think this is not worth the effort. >> if there were a way to provide instrictions, it would encourages >> developer to write more messages I suppose. Sure, but analogous to port developers making patches that they don't try to send to upstream developers is a problem, making our own docs has some pitfalls too since sometimes we are doing what the developers should have (when it isn't stuff that is MacPorts specific). And I'm a little more pessimistic that creating a infrastructure will spur people to write more hints and docs because it takes time, patience, and they need to be updated once created. But I'm in no way opposed to doing anything that helps; I probably do more doc writing than any other port author. I'm all for anything doc related that helps that we can agree on as long as it is efficient and sustainable. > >One option would be to simply hold back any message until all ports >installed and output them afterwards. So all messages would be at the >end of the log. > >Or, use some new target like print_message {}, but which would need to >be stored in the registry after installation to be always available in >the state as it was on install. I like these types of things. > >For this rather long nedi help, I would prefer to put them into some >file like /opt/local/share/doc/nedi/INSTALL.macports and just print a >message that there is additional help in this file. Yes, but if you want variables evaluated within the instructions, and I do, then you end up doing reinplace on keywords so you add another file to ${files} and require more coding and probably some errors in the process. So now you've got to debug the instructional phase. I prefer it either as it is (ui_msg) or by adding a command that would crank out and evaluate the ui_msg section on the fly after a port is installed. Mark

1 0

How should MacPorts show users instruction messages (was: user instructions - was ... mysql5 + php5 + apache2)
by js 29 Feb '08

29 Feb '08

I don't think this is not worth the effort. if there were a way to provide instrictions, it would encourages developer to write more messages I suppose. On 2/29/08, markd(a)macports.org <markd(a)macports.org> wrote: > >> > The problem is that if you do miss these messages, then you can't > >> > easily resurrect them other than installing the whole lot again. > >> > >> > >> True-ish. Well really you only need to deactivate and active the port > >> again, since ports print such messages in the post-activate phase. > >> But users don't know that. You could also read the portfile source > >> code, but that's not really a clean solution either. Any suggestions > >> for how we could improve this situation? > > > >How about including some instructions like this in ports and > >install it in /opt/local/share/someplace? > > > >README.macports or something like that. > > It would be cool if the ui_msgs could be spit out using a port command, > say 'port foo msg' or some such. I use user_msg in Portfiles for > extensive documentation, a Howto really, on configuring some ports. For > example: > http://trac.macports.org/projects/macports/browser/trunk/dports/net/nedi/Po… > > Though not many do this, it can be a HUGE timesaver for users. But since > comparatively few ports have extensive ui_msg's, perhaps it isn't worth > the effort. And it would be a low priority for the MP coders since there > are other more foundational things to do. And I think evaluating > variables might present some problems too. I usually use 'port ed foo' to > look at the ui_msg's in another window. > > Mark > >

2 4

Macports open tickets
by Thomas Reifferscheid 29 Feb '08

29 Feb '08

As some of you might allready know, there are some graphs showing the macports open tickets over time. You find the graphs here: http://student.physik.uni-mainz.de/~reiffert/macports/ Feel free to comment or improve. You'll find all the details on that site. Kind regards Thomas

1 0

Trac ticket that need your attension
by js 29 Feb '08

29 Feb '08

1 0