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 with the changes I made to the KDE Wiki yesterday? Re the unfinished "List of ports" section, maybe we could flesh out https://trac.macports.org/wiki/KDEPackages, which is already a good start, and just have a link to it in https://trac.macports.org/wiki/KDE I would be happy to add a section for KDE Games … :-) Maybe the KDEPackages page should follow the structure of the KDE Projects pages. Also, I would like to add links to our MacPorts KDE pages into KDE's page about Apple Mac (http://community.kde.org/Mac?id=build) and tell [email protected] list. Cheers, Ian W. > On Mar 5, 2013, at 1:21 PM, Jeremy Lavergne <[email protected]> > wrote: > >>> I think they convey the right air of dampening down end-users' expectations >>> (recall two recent examples of those on macports-users). >> >> We might might as well lament "you must run the MacPorts installer" as we're >> not bundled with OS X. >> >>> I do not think those words are any reflection on the power of MacPorts, but >>> I would >>> be happy to qualify them in some way if others think that. >> >> I fear it's ambiguous and distracting because the definition of "out of the >> box" could be interpreted as any number of things. I don't feel it >> contributes to the "How do I setup KDE?" conversation and is >> commentary—which I share I wouldn't put in a "how to" wiki. >> >> _______________________________________________ >> macports-dev mailing list >> [email protected] >> https://lists.macosforge.org/mailman/listinfo/macports-dev > _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
