Hi all,
I'm interested in experimenting with a MAMP-like installation,
substituting Nginx for Apache.
Anything special I should know? I've done a number of MAMPs with MacPorts.
TIA.
___
macports-users mailing list
macports-users@lists.macosforge.or
On Thu, Dec 13, 2012 at 9:23 PM, Behrang Saeedzadeh wrote:
> Would it be possible to add Google Dart to MacPorts?
>
File a ticket at https://trac.macports.org requesting it. It'll happen
faster if you provide a Portfile (http://guide.macports.org/#development).
--
brandon s allbery kf8nh
Hi,
Would it be possible to add Google Dart to MacPorts?
Cheers,
Behrang Saeedzadeh
http://www.behrang.org
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Hello,
On 2012-12-13 17:10, Enrico Placci wrote:
> I was looking for the images of my installed ports when I stumbled on
> https://trac.macports.org/ticket/13143
> Is there a way to revert to the original behaviour? How is the new
> behaviour different from direct + archived packages?
> It seems t
On Dec 13, 2012, at 11:10 AM, Enrico Placci wrote:
> It seems to me the best solution would have just been to change the
> default settings (to direct + archived , so to not conflict with that
> broken backup system by default) and leave the choice to the users.
The way things work now is basical
> I was looking for the images of my installed ports when I stumbled on
> https://trac.macports.org/ticket/13143
> Is there a way to revert to the original behaviour? How is the new
> behaviour different from direct + archived packages?
> It seems to me the best solution would have just been to cha
Hello,
I was looking for the images of my installed ports when I stumbled on
https://trac.macports.org/ticket/13143
Is there a way to revert to the original behaviour? How is the new
behaviour different from direct + archived packages?
It seems to me the best solution would have just been to change
