ports/179267: UPDATING: entry for www/magento

[Melvyn Sopacua]

>Number:         179267
>Category:       ports
>Synopsis:       UPDATING: entry for www/magento
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 03 18:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Melvyn Sopacua
>Release:        FreeBSD 9.1-RELEASE amd64
>Organization:
>Environment:
System: FreeBSD fire.magemana.nl 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root at farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
When I took maintainership I've modified the port to be more conservative in
it's file permissions. This has consequences for upgrades.

>How-To-Repeat:
>Fix:
I believe the following would be a good entry for UPDATING.

20130603:
  AFFECTS: users of www/magento
  AUTHOR: melvyn at magemana.nl

  Magento has been updated to 1.7.0.2. With it a stricter file system policy
  is enforced on the port. If you (or your customer) rely heavily on 
  Magento Connect via the backend to install extensions, your quickfix is:
  
  # chown -R www: ${PREFIX}/www/magento
  # chmod -R u+w ${PREFIX}/www/magento

  The more conservative approach:
  # chown -R www: ${PREFIX}/www/magento/app/code/{local,community} \
      ${PREFIX}/www/magento/app/{design,locale} \
      ${PREFIX}/www/magento/{downloader,skin}
  # chmod -R u+w ${PREFIX}/www/magento/app/code/{local,community} \
      ${PREFIX}/www/magento/app/{design,locale} \
      ${PREFIX}/www/magento/{downloader,skin}

  The conservative aproach will alert you to extensions that try to write in
  Magento core, while allowing clean extensions to install properly (corner
  cases may exist).


>Release-Note:
>Audit-Trail:
>Unformatted: