Tag Info

Hot answers tagged

10

You are very close. Try this instead: make all-depends-list That will recurse through all dependencies and print them for you. To test different build scenarios and how they affect the dependency list, try things like: make NOPORTDOCS=yes NOPORTEXAMPLES=yes all-depends-list make WITHOUT_X11=yes all-depends-list Here is the full set of dependency ...


7

No upgrades are "mandatory" -- If the port version you're using works, no dependencies require the newer version, and there are no security holes you don't need to upgrade anything. If you're asking about mandatory changes (e.g. new configuration files) as a result of a port upgrade, UPDATING is the right place to look, and there's also often something in ...


6

see /usr/ports/UPDATING the entry from 20120630 has detailed description how to do it with portmaster or portupgrade


6

Generally, you can consult the contents of the /usr/ports/UPDATING file on how to deal non-trivial upgrades. Usually, it provides solutions for users that are using portupgrade, portmaster or binary pkgng packages. Here are the instructions from the 20130612 entry in the UPDATING file: ... Please rebuild all Perl ports and all ports that depend on it: ...


5

First, you can select any option the system presents you with. Port maintainers take a great deal of time to make sure that the options presented work (or mark them as broken/experimental). If you're compiling stuff from ports we generally assume you want these options so you can customize the installation to suit your environment. To answer your ...


5

Try portupgrade -f /var/db/pkg/p5*. This will rebuild all your installed p5* ports. portupgrade is not part of the base system. You can find this port in ports-mgmt/portupgrade.


4

You can install an individual package using the pkg_add command, like this: pkg_add -r <package> The -r option asks pkg_add to fetch the package over the network. For example, to install bash: pkg_add -r bash As with many things FreeBSD, this is documented in the FreeBSD handbook, specifically in the section titled Using the Packages System. ...


4

Yes, if two ports have the same dependancy, try to build it at the same time, one or both builds will fail. It's better to build ports serially (making a meta port of all the ports you want to install is a good idea if you're going to do it on several machines) and run make with a -j # to increase concurrency where it's able .


4

Next time run make all-depends-list before you start building the port. If you don't like what you see on the list don't go any further. This and other gems can be found in /usr/ports/Mk/bsd.port.mk. Not friendly reading though. You're mildly screwed in terms of cleaning up the mess. You really have two options that I can think of: Option 1 - Run the ...


4

How do we get back to the initial options screen? You need to reconfigure the php53 port, but it seems you've been trying to reconfigure a module instead. Perform the following cd /usr/ports/lang/php53 make config You can also use make showconfig, make rmconfig to show and delete options, respectively. Where are these config files saved? ...


4

I think you're looking for /etc/make.conf.


3

Here's the .. more manual way to do it. perl-after-upgrade is supposed to do the trick for most files (excepting binaries like irssi), however, I find it doesn't work so well anymore, so I just do everything by hand. Before upgrading perl, I would shut down anything that depends on it, since those things are likely to break while the upgrade process is ...


3

Yes, there are several ways. The most straight foward would probably be to setup a 32bit chroot or jail and build the package in there via make package. Another way is to use one of the many tools in the ports-mgmt category, such as tinderbox or poudriere which are designed for building packages.


3

Set for example: DEFAULT_VERSIONS= perl5=5.18 ruby=2.0 in your /etc/make.conf This information is taken from /usr/ports/Mk/bsd.default-versions.mk # $FreeBSD: head/Mk/bsd.default-versions.mk 345909 2014-02-25 00:32:09Z gerald $ # # MAINTAINER: ports@FreeBSD.org # # Provide default versions for ports with multiple versions selectable # by the user. # ...


3

You can look in /usr/ports/Mk/bsd.*.mk for corresponding variables and set them in /etc/make.conf. But it's safer to just install needed versions of such software and then continue with everything else.


3

Please check the following section of the FreeBSD handbook: Chapter 4 Installing Applications: Packages and Ports (Yes, a bit RTFM, but the Handbook is really, really good)


3

This is from the EXAMPLES section of the portmaster man page: First, get a list of installed ports: portmaster --list-origins > installed-port-list On your target system, use that list as input to portmaster: portmaster `cat installed-port-list`


3

This is because you will be running the Linux version, and currently the Linux "emulator" for FreeBSD currently only supports 32bit Linux. (I put "emulator" in quotes because it's not really an emulator, it's really just a syscall translator. And there's work to add 64bit Linux support going on, but until then only 32bit Linux binaries can be run.) ...


2

Here's a lightly-tested solution: #!/bin/sh # Build a regex to match all the .pm files _regex="" for arg in $*; do arg=`echo ${arg} | sed -e 's|::|/|g'` if [ "X${regex}X" != "XX" ]; then regex="${regex}|" fi regex="${regex}(${arg})" done regex="%%SITE_PERL%%/(${regex}).pm" # Find the .pm files and derive the port names from them, ...


2

Firstly I should say that I don't use portmaster, I use portupgrade, but then I build ports rather than use packages! Portupgrade allows you to put: portupgrade php\* which will upgrade all the php ports. Portmaster may do the same thing. Also you can give portsnap multiple commands in one go, so you can put portsnap fetch update


2

In regards to software, When using "port" as a noun in regards to FreeBSD, it is a piece of software that has been modified so it will easily compile, install and run. FreeBSD comes with a set of directories that contain thousands of such pieces of software located in /usr/ports by default. Precompiled versions of the software are usually available as ...


2

try the rehash command, your shell is most likely keeping a cache of executables within your PATH.


2

Did you look at 00FAQ as was suggested by the error message? Question 8.6 describes exactly your situation and how to work around it. If you don't want to install the Kernel source on your machine, a workaround would be to install the lsof binary package pkg_add -r lsof


2

You need to update your port tree. Run: portsnap fetch update If you want to keep your port tree updated on a regular basis you can create a periodic script. This is the script I use on my dev machine, /usr/local/etc/periodic/weekly/910.portsnap #!/bin/sh - # # # If there is a global system configuration file, suck it in. # if [ -r ...


2

Diablo JDK/DRE is horribly outdated. Don't use it. Install java/openjdk6 instead (or java/openjdk7 if you want the devel version) If these do not appear in your ports tree (as you're using a similarly horribly outdated, unsupported version of FreeBSD with known security vulnerabilities) you'll need to update it with cvsup, csup, or portsnap (not sure if it ...


2

Your best bet would be as Hennes suggests: Create a jail for each version of Apache+PHP you want to use. This has a number of advantages, the two biggest ones being isolation (if your PHP 5.2 sites get hacked the damage is contained to the PHP 5.2 Jail) and management simplicity (treat the jails like they're two separate FreeBSD installations -- one running ...


2

ls -Alt /var/db/pkg | grep '/$' | tail -n 20 should show 20 oldest apps installed from ports. Also, pkg_version -vIL= command could be usefult to compare versions of installed ports and ports in updated tree.


2

I don't use nginx (and therefore don't use the port), but looking at the port it does the "standard" thing of copying the dist files over as the "live" files for a fresh install. The maintainer specified the -p flag in doing this, which preserves the file mode, so the resulting "live" files are read-only. There is no reason you can't make these files ...


2

If you have a patch ready to update the port to 5.5.32, create a PR and email the maintainer of the port. If you don't have a patch ready, email the maintainer of the port and ask politely of an update if it's very urgent for you.



Only top voted, non community-wiki answers of a minimum length are eligible