Re: KDE instructions

2013-03-02 Thread Ian Wadham
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. I do not have edit access to an

Re: KDE instructions

2013-03-02 Thread Lawrence Velázquez
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. I do not have edit access to anything in MacPorts. > > So how would you like me to proceed?

Re: KDE instructions

2013-03-02 Thread Ian Wadham
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

Re: [MacPorts] #38255: The port lang/chicken is not indexed by default

2013-03-02 Thread Lawrence Velázquez
On Mar 2, 2013, at 7:40 PM, MacPorts wrote: > #38255: The port lang/chicken is not indexed by default > + > Reporter: dtakahashi42@… | Owner: macports-tickets@… > Type: defect | Status: new > Priority: Normal

Re: [103579] trunk/dports/devel/libftdi/Portfile

2013-03-02 Thread Jeremy Lavergne
> The library name changed to libftdi1 now for both the .dylib file and > the pkg-config .pc files. Thus, this requires at least a patch now in > dependents to change to -lftdi1 for linking. > > This update broke building openocd +ft2232 as it cannot find libftdi. > The other dependent urjtag stil

Re: [103579] trunk/dports/devel/libftdi/Portfile

2013-03-02 Thread Rainer Müller
On 2013-03-01 23:21, s...@macports.org wrote: > Revision: 103579 > https://trac.macports.org/changeset/103579 > Author: s...@macports.org > Date: 2013-03-01 14:21:52 -0800 (Fri, 01 Mar 2013) > Log Message: > --- > libftdi: update to 1.0 > > Modified Paths: > --

Re: [103586] trunk/dports/python/py-xlrd/Portfile

2013-03-02 Thread Jeremy Lavergne
> I think this "archive" thing is part of the new layout they rolled out a few > months ago: > > https://trac.macports.org/ticket/36862 > > I did not investigate switching to this layout because the old way seemed to > still work, and this would mean changing every port since checksums change.

Re: can someone try a sysctl under MacOS 10.5/x86

2013-03-02 Thread Ryan Schmidt
On Mar 2, 2013, at 12:21, Vincent Habchi wrote: > AFAIK, 10.4 does not run on x86? Can you confirm this? The first Intel Macs shipped in January 2006 and 10.5 didn't ship until October 2007. So there were many generations of Intel Macs that shipped with 10.4, as did the first Apple TV. Here's

Re: can someone try a sysctl under MacOS 10.5/x86

2013-03-02 Thread Vincent Habchi
Thanks Ryan, that’s *very* kind of you. AFAIK, 10.4 does not run on x86? Can you confirm this? Cheers! Vincent ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [103586] trunk/dports/python/py-xlrd/Portfile

2013-03-02 Thread Jeremy Lavergne
> Why were these master_sites and distname lines necessary? With the github > portgroup you shouldn't need to add those; the defaults should work. If I > remove these lines, the checksums then differ, but the contents of the files > are the same. It's the same as the github.master_sites except

Re: can someone try a sysctl under MacOS 10.5/x86

2013-03-02 Thread Ryan Schmidt
On Mar 2, 2013, at 10:59, Vincent Habchi wrote: > Can someone do a: > > sysctl -a | grep optional > > under a 10.5/x86 system and tell me what’s output? hw.optional.x86_64: 1 hw.optional.sse4_2: 1 hw.optional.sse4_1: 1 hw.optional.supplementalsse3: 1 hw.optional.sse3: 1 hw.optional.sse2: 1 hw.

Re: [103586] trunk/dports/python/py-xlrd/Portfile

2013-03-02 Thread Ryan Schmidt
On Mar 2, 2013, at 11:37, Jeremy Lavergne wrote: >> Why were these master_sites and distname lines necessary? With the github >> portgroup you shouldn't need to add those; the defaults should work. If I >> remove these lines, the checksums then differ, but the contents of the files >> are the

can someone try a sysctl under MacOS 10.5/x86

2013-03-02 Thread Vincent Habchi
Hi everybody, I would like to know if MacOS Leopard on i386 or x86-64 has sysctl to detect x86 vectorizing units (sse). Unfortunately, the only computer I have running Leopard is a MacPro G5, and obviously these sysctl are missing (instead there is a hw.optional.altivec sysctl). Can someone do

Re: [103572] trunk/dports/net/nedi/Portfile

2013-03-02 Thread Ryan Schmidt
On Mar 1, 2013, at 14:04, ma...@macports.org wrote: > Revision: 103572 > https://trac.macports.org/changeset/103572 > Author: ma...@macports.org > Date: 2013-03-01 12:04:25 -0800 (Fri, 01 Mar 2013) > Log Message: > --- > Update notes section only. > > Modified Paths: > ---

Re: [103586] trunk/dports/python/py-xlrd/Portfile

2013-03-02 Thread Ryan Schmidt
On Mar 1, 2013, at 17:34, s...@macports.org wrote: > Revision: 103586 > https://trac.macports.org/changeset/103586 > Author: s...@macports.org > Date: 2013-03-01 15:34:06 -0800 (Fri, 01 Mar 2013) > Log Message: > --- > py-xlrd: update to 0.9.0, supports python 2.6 2.7 3.2+ >

Re: KDE instructions

2013-03-02 Thread Nicolas Pavillon
Great, I did not know that there was this automated monitoring. Handy. 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

Re: KDE instructions

2013-03-02 Thread Ryan Schmidt
On Mar 2, 2013, at 05:54, Ian Wadham wrote: > I do not know how to write wikis It's not too difficult. Mostly you can just write paragraphs. When you need special formatting, consult this page: https://trac.macports.org/wiki/WikiFormatting ___ macp

Re: KDE instructions

2013-03-02 Thread Ian Wadham
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