[MacPorts] #28192: glib2 @2.26.1_1 did not activate
MacPorts
noreply at macports.org
Fri Jan 28 16:24:41 PST 2011
#28192: glib2 @2.26.1_1 did not activate
--------------------------------------+-------------------------------------
Reporter: Peter_Dyballa@… | Owner: ryandesign@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Keywords: | Port: glib2
--------------------------------------+-------------------------------------
Comment(by Peter_Dyballa@…):
Replying to [comment:11 ryandesign@…]:
> The process for returning to a previous version of a port is documented
in the wiki page [wiki:howto/InstallingOlderPort
howto/InstallingOlderPort].
>
I remembered later that the pervious version is kept on disk...
>
> The reason having Fink and MacPorts installed at the same time is not
supported is that software installed with Fink can cause unexpected
failures building software with MacPorts. "Not supported" means it might
work, but we can't help you if it doesn't. I strongly recommend you decide
whether to use MacPorts or Fink, and uninstall the other. If the reason
you were using Fink is that it has software you need that is not in
MacPorts, you can file port request tickets in our issue tracker; maybe we
can add that software to MacPorts.
It's easy for me to have interactively both sorts of software (plus that
from Apple) in a shell and when compiling and installing software
separating (or mixing) them all. That's really no big thing. What concerns
me more, is that the software archives are scattered over the file system
(otherwise I could outsource them partially on a rewritable DVD and have
more disk space) and there doesn't seem to be a system to manage the many
versions of these archives. MacPorts is so silly, that when upgrading or
installing software fetches them on demand from the internet so that I
need to stay in internet for long and indeterminate periods. And I never
get a hint that this upgrade or installation would install GB of data
without asking me whether I really want do that. And this happens quite
often with xorg-server and its many components.
And I want to find out whether it works to create my own Portfiles to
update or get some packages (gnutls, libm17n, gkrellm plugins)!
BTW, I did not force activation after I saw the two package versions
installed on disk in order find out what might have caused the activation
failure. I usually really don't like force.
--
Ticket URL: <https://trac.macports.org/ticket/28192#comment:12>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list