Re: Serious problems updating Current after switching to libxul.

[Matthew Seaman]

keneasson wrote:

Can anyone help me get my system back up and running?

make.conf looks like this:
WITH_MYSQL_VER=51
APACHE_VERSION=22
OVERRIDE_LINUX_BASE_PORT=f8
WWWDIR = /web/phpmyadmin
WITH_CUPS="yes"
CUPS_OVERWRITE_BASE=true
#NO_LPR=true
USE_GECKO=libxul

^^^^^^^^^^^^^^^^^
This is your problem.  You want to say:

 WITH_GECKO=libxul

here.

# Begin portconf settings
# Do not touch these lines
.if !empty(.CURDIR:M/usr/ports*) && exists(/usr/local/libexec/portconf)
_PORTCONF!=/usr/local/libexec/portconf
.for i in ${_PORTCONF:S/|/ /g}
${i:S/%/ /g}
.endfor
.endif
# End portconf settings
# added by use.perl 2009-09-19 16:22:20
PERL_VERSION=5.10.1

In general, you *never* add any USE_FOO flags to /etc/make.conf -- USE_FOO

generally does dramatic things like adding dependencies on whole
software subsystems.  Your 'USE_GECKO' setting in /etc/make.conf (which has

bit of brokenness.

Instead, you need a WITH_FOO flag.  WITH_FOO is designed for end users to
tweak the way ports work in detail: they only have any effect in ports that
are specifically written to take notice of them; everything else will just 
ignore them.  Even so, it's very common to use directory matching login or,
as you have, things like PORTCONF to limit the application of a WITH_FOO
flag to a specific port.  The whole OPTIONS dialogue system is just a
front-end to setting WITH_FOO flags for a specific port.

Note: something that may cause a certain amount of astonishment to neophyte
users.  The opposite of saying:

WITH_FOO=yes

is not:

WITH_FOO=no   ### Don't do this.

but:

WITHOUT_FOO=yes   ### Do this.



        Cheers,

        Matthew

--
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                 Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                 Kent, CT11 9PW

is designed for use by port maintainers inside the limited scope of port-specific Makefiles: the presence of a USE_FOO setting in scope effect in the global scope) has made *every* port on your machine depend on gecko related libraries. It's not really surprising you're experiencing a That's because the value of 'WITH_FOO' variables is not actually tested anywhere, only whether the variable is defined or not. Setting WITH_FOO=bananas would have exactly the same effect, as, indeed does WITH_FOO=no or WITH_FOO=over_my_dead_body

signature.asc
Description: OpenPGP digital signature