local PortGroup repo?

[David Strubbe]

I tried it out, and it works partially. The PortGroup file I made in
_resources/port1.0/group/fortran-1.0.tcl is recognized when installing, but
not when uninstalling. For example:

$ sudo port uninstall libxc @2.0.2_0+gcc47
Warning: PortGroup fortran 1.0 could not be located. fortran-1.0.tcl does
not exist.
Error: org.macports.uninstall for port libxc returned: Registry error:
libxc @2.0.2_0 not registered as installed
Please see the log file for port libxc for details:

/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_libxc_2.0.2_0+gcc47/libxc/main.log
Warning: Failed to execute portfile from registry for libxc @2.0.2_0+gcc47
Warning: PortGroup fortran 1.0 could not be located. fortran-1.0.tcl does
not exist.
Error: org.macports.deactivate for port libxc returned: Active version of
libxc is not 2.0.2_0 but 2.0.2_0+gcc47.
Please see the log file for port libxc for details:

/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_libxc_2.0.2_0+gcc47/libxc/main.log
Warning: Failed to execute portfile from registry for libxc @2.0.2_0+gcc47
--->  Deactivating libxc @2.0.2_0+gcc47
--->  Uninstalling libxc @2.0.2_0+gcc47

The log file mentioned doesn't contain much more information:

$ cat
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_libxc_2.0.2_0+gcc47/libxc/main.log
version:1
:debug:main Executing org.macports.main (libxc)
:debug:deactivate deactivate phase started at Tue Nov 12 00:37:14 EST 2013
:debug:deactivate Executing org.macports.deactivate (libxc)
:error:deactivate org.macports.deactivate for port libxc returned: Active
version of libxc is not 2.0.2_0 but 2.0.2_0+gcc47.
:debug:deactivate Error code: NONE
:debug:deactivate Backtrace: Active version of libxc is not 2.0.2_0 but
2.0.2_0+gcc47.
    invoked from within
"registry_deactivate $subport $version $revision $portvariants [array get
user_options]"
    (procedure "portdeactivate::deactivate_main" line 11)
    invoked from within
"$procedure $targetname"
:info:deactivate Warning: targets not executed for libxc:
org.macports.deactivate
:notice:deactivate Please see the log file for port libxc for details:

/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_libxc_2.0.2_0+gcc47/libxc/main.log



On Sat, Nov 2, 2013 at 8:04 AM, Rainer Müller <raimue at macports.org> wrote:

> On 2013-11-01 21:02, Dan Ports wrote:
> > On Fri, Nov 01, 2013 at 03:21:36PM -0400, Eric Gallager wrote:
> >> Really? That's strange, I could've sworn I was able to use the qmake
> >> portgroup in my local PortFile repository successfully when I was
> testing
> >> it...
> >
> > I believe portfiles will use portgroups from their own repository, so
> > portgroups in a local repository will affect your local ports but not
> > override ones in the default repo.
>
> Yes, port groups will be used from their own ports tree. Only if the
> port group file does not exist there, it falls back to using the port
> group from the default ports tree. This is the same behavior that is
> applied for all files in the _resources directory.
>
> I added a debug message in r112824 [1], which makes it easier to see
> which port groups are sourced.
>
> Rainer
>
> [1] https://trac.macports.org/changeset/112824
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20131112/b606d40f/attachment.html>