Re: KDE instructions
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 anything in MacPorts. >> >> So how would you like me to proceed? > > Anyone with a Trac account can edit the wiki; just click the "Edit this page" > button at the bottom-left of any page. Thanks, Lawrence. My login for submitting tickets is enough to get that … :-) Cheers, Ian W. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: KDE instructions
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? Anyone with a Trac account can edit the wiki; just click the "Edit this page" button at the bottom-left of any page. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: KDE instructions
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 incomplete or inaccurate. Please feel free to edit/correct them. I > will also expand the ports list in order to try to have something describing > the maze of KDE ports. 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? Cheers, Ian W. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [MacPorts] #38255: The port lang/chicken is not indexed by default
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 | Milestone:
> Component: ports |Version: 2.1.3
> Keywords: | Port: chicken
> +
> The port lang/chicken seems not to be included into the default index. As
> a result, {{{port search chicken}}} does not find chicken scheme.
> {{{
> $ sudo port selfupdate
> ---> Updating MacPorts base sources using rsync
> MacPorts base version 2.1.3 installed,
> MacPorts base version 2.1.3 downloaded.
> ---> Updating the ports tree
> ---> MacPorts base is already the latest version
>
> The ports tree has been updated. To upgrade your installed ports, you
> should run
> port upgrade outdated
> $ port search chicken
> cotvnc @2.0b4 (aqua, vnc)
> Chicken of the VNC is a VNC client for Mac OS X
>
> swig-chicken @2.0.9 (devel)
> Chicken binding for swig
>
> Found 2 ports.
> }}}
Could someone help me out on this ticket? The problem is probably one of the
changes I made recently (r103366, r103368, r103386), but I have no idea which.
vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [103579] trunk/dports/devel/libftdi/Portfile
> 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 still builds, but as libftdi cannot be found > the support for FTDI is missing. > > I am not able to check whether OpenOCD still works with libftdi1 at the > moment as I do not have any device with me. > > Maybe we should be keep a libftdi0 port for the older branch? Sure, I'd epoch+ this one back to where it was and create a new libftdi1. Sound good? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [103579] trunk/dports/devel/libftdi/Portfile
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: > -- > trunk/dports/devel/libftdi/Portfile 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 still builds, but as libftdi cannot be found the support for FTDI is missing. I am not able to check whether OpenOCD still works with libftdi1 at the moment as I do not have any device with me. Maybe we should be keep a libftdi0 port for the older branch? Rainer ___ 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
> 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. > > I have no idea what the github servers do behind the servers w.r.t. > dynamically generating tarballs or not. I'll fetch and checksum later today (currently they continue to match) and see if it changed; it's likely they're equivalent with different creation methods (internally, one from `git archive` versus `git checkout ... && rm -rf .git`). I'll see if I can't dig up info on their blog or contact them to find out their plans for archive and tarball. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: can someone try a sysctl under MacOS 10.5/x86
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 what I get on my MacBookPro3,1 when booted from its 10.4 Install DVD: hw.optional.floatingpoint: 1 hw.optional.mmx: 1 hw.optional.sse: 1 hw.optional.sse2: 1 hw.optional.sse3: 1 hw.optional.x86_64: 1 hw.optional.supplementalsse3: 1 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: can someone try a sysctl under MacOS 10.5/x86
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
> 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 that it uses the "archive" from the site, rather than "tarball". I went with this because that's the link on the site, which shouldn't be recreated dynamically... Do we know which is not the dynamic one? ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: can someone try a sysctl under MacOS 10.5/x86
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.optional.sse: 1 hw.optional.mmx: 1 hw.optional.floatingpoint: 1 ___ 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
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 same. > > It's the same as the github.master_sites except that it uses the "archive" > from the site, rather than "tarball". I went with this because that's the > link on the site, which shouldn't be recreated dynamically... > > Do we know which is not the dynamic one? 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. I have no idea what the github servers do behind the servers w.r.t. dynamically generating tarballs or not. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
can someone try a sysctl under MacOS 10.5/x86
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 a: sysctl -a | grep optional under a 10.5/x86 system and tell me what’s output? Thanks a lot. Vincent ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: [103572] trunk/dports/net/nedi/Portfile
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:
> --
>trunk/dports/net/nedi/Portfile
>
> Modified: trunk/dports/net/nedi/Portfile
> ===
> --- trunk/dports/net/nedi/Portfile2013-03-01 19:38:18 UTC (rev 103571)
> +++ trunk/dports/net/nedi/Portfile2013-03-01 20:04:25 UTC (rev 103572)
> @@ -124,42 +124,47 @@
> sudo ${prefix}/lib/mysql5/bin/mysqladmin -u root password
>
>
> -2) Install PHP5 with SNMP support and Apache 2
> +2) Install PHP5 with SNMP support and MacPorts Apache
>
> sudo port install php5 +apache2 +mysql5 +snmp
Please update this port to use the new php53/php54/php55 and
mysql51/mysql55/mariadb/percona ports and variants.
> + Add an alias statement:
> + Alias /nedi \"/opt/local/share/nedi/html\"
MacPorts might not be installed in /opt/local; please use ${prefix}.
___
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
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+
>
> Modified Paths:
> --
>trunk/dports/python/py-xlrd/Portfile
>
> Modified: trunk/dports/python/py-xlrd/Portfile
> ===
> --- trunk/dports/python/py-xlrd/Portfile 2013-03-01 23:22:04 UTC (rev
> 103585)
> +++ trunk/dports/python/py-xlrd/Portfile 2013-03-01 23:34:06 UTC (rev
> 103586)
> @@ -3,10 +3,12 @@
>
> PortSystem 1.0
> PortGroup python 1.0
> +PortGroup github 1.0
>
> +github.setuppython-excel xlrd 0.9.0
> +master_sites${github.homepage}/archive/[join ${github.tag_prefix}
> ""]${github.version}
> distnamexlrd-${version}
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.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: KDE instructions
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 be incomplete or inaccurate. Please feel free to edit/correct them. I will also expand the ports list in order to try to have something describing the maze of KDE ports. I indeed do not hope that users will fall on this page directly, but it could be handy to have it to redirect questions, instead of repeating the same answers several times, or receive complaints because the information was not out there. Cheers, Nicolas On Mar 2, 2013, at 8:54 PM, Ian Wadham wrote: > 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 we have an extensive page in the wiki >>> concerning gnome (https://trac.macports.org/wiki/GNOME), KDE just links to >>> the somewhat outdated external page of KDE about Mac. >>> >>> I am not sure anymore about the policy concerning the wiki. May I create >>> directly the page and gather the information on a new page dedicated to >>> KDE, or is there a validation procedure, since it is not monitored through >>> commits like the Macports Guide ? >> >> Changes to the wiki do get sent to the macports-changes mailing list, just >> like commits to the repository. Please feel free to create wiki pages and >> write documentation to your heart's content! > > And if you need any help, review, etc. please let me know. Unfortunately, I > do not > know how to write wikis, but I do know a little about KDE and the KDE > project, so > maybe I can get some questions answered. > > I am not sure if anyone new to KDE apps will see the proposed wiki before they > jump in at the deep end and try to get digikam or kdenlive installed and > running > and then get into trouble (as has happened just recently). But the wiki will > be a > valuable resource to show them after the event and help them recover. > > All the best, Ian W. > KDE Games Developer > > > > ___ > 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: KDE instructions
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 ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: KDE instructions
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 we have an extensive page in the wiki >> concerning gnome (https://trac.macports.org/wiki/GNOME), KDE just links to >> the somewhat outdated external page of KDE about Mac. >> >> I am not sure anymore about the policy concerning the wiki. May I create >> directly the page and gather the information on a new page dedicated to KDE, >> or is there a validation procedure, since it is not monitored through >> commits like the Macports Guide ? > > Changes to the wiki do get sent to the macports-changes mailing list, just > like commits to the repository. Please feel free to create wiki pages and > write documentation to your heart's content! And if you need any help, review, etc. please let me know. Unfortunately, I do not know how to write wikis, but I do know a little about KDE and the KDE project, so maybe I can get some questions answered. I am not sure if anyone new to KDE apps will see the proposed wiki before they jump in at the deep end and try to get digikam or kdenlive installed and running and then get into trouble (as has happened just recently). But the wiki will be a valuable resource to show them after the event and help them recover. All the best, Ian W. KDE Games Developer ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
