[87201] trunk/dports/aqua/qlipper/Portfile

[Ryan Schmidt]

On Nov 13, 2011, at 23:06, pvanek at macports.org wrote:

> Revision: 87201
>          http://trac.macports.org/changeset/87201
> Author:   pvanek at macports.org
> Date:     2011-11-13 21:06:30 -0800 (Sun, 13 Nov 2011)
> Log Message:
> -----------
> qlipper: buildbot fix (case sensitive paths)
> 
> Modified Paths:
> --------------
>    trunk/dports/aqua/qlipper/Portfile
> 
> Modified: trunk/dports/aqua/qlipper/Portfile
> ===================================================================
> --- trunk/dports/aqua/qlipper/Portfile	2011-11-14 05:03:53 UTC (rev 87200)
> +++ trunk/dports/aqua/qlipper/Portfile	2011-11-14 05:06:30 UTC (rev 87201)
> @@ -3,8 +3,9 @@
> PortSystem              1.0
> PortGroup               qt4 1.0
> 
> -name                    qlipper
> +name                    Qlipper
> version                 1.8.2
> +revision                1

I wasn't sure what would happen when you change the case of the port name like that. Will users who had qlipper @1.8.2_0 installed get prompted to upgrade to Qlipper @1.8.2_1? I don't think this is a case we ever deliberately considered, so if it does work, it probably works by coincidence (though I'm not opposed to making this a supported kind of change).

I tried it out, and on my system at least it works:

$ port installed qlipper
The following ports are currently installed:
  qlipper @1.8.2_0+universal (active)
$ sudo port sync
$ port outdated qlipper
The following installed ports are outdated:
qlipper                        1.8.2_0 < 1.8.2_1         
$ sudo port -u upgrade qlipper
Password:
--->  Computing dependencies for Qlipper
--->  Fetching archive for Qlipper
--->  Attempting to fetch Qlipper-1.8.2_1+universal.darwin_10.i386-x86_64.tbz2 from http://packages.macports.org/Qlipper
--->  Fetching Qlipper
--->  Verifying checksum(s) for Qlipper
--->  Extracting Qlipper
--->  Configuring Qlipper
--->  Building Qlipper
--->  Staging Qlipper into destroot
--->  Installing Qlipper @1.8.2_1+universal
--->  Cleaning Qlipper
--->  Computing dependencies for Qlipper
--->  Deactivating qlipper @1.8.2_0+universal
--->  Activating Qlipper @1.8.2_1+universal
--->  Cleaning Qlipper
--->  Uninstalling qlipper @1.8.2_0+universal
$ 

I don't know if it would still work on a case-sensitive filesystem, and I don't know if fixing #31743 would break this.

In any case, the port directory now doesn't match the port name:

$ port lint Qlipper
--->  Verifying Portfile for Qlipper
Error: Portfile directory qlipper does not match port name Qlipper
--->  1 errors and 0 warnings found.