Hot answers tagged


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 ...


My suggestion would be pkg_cutleaves (available in the ports collection), or pkg-orphan -- Both of these do the same basic thing (list packages that aren't referred to as a dependency by any other package, and ask you what to do). I wouldn't bother though: The build dependencies will just have to be rebuilt and reinstalled when you upgrade the port, and ...


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 ...


Sequentially: portmaster --check-depends portmaster --check-port-dbdir portmaster -s portmaster -y --clean-distfiles


The best option (IMHO) is to set all the options at the very start. You can do this by running make config-recursive.


Just add BATCH=1 to /etc/make.conf.


How can I configure FreeBSD to clean distfiles after installing a port (using make, portupgrade, etc)? If "after installing a port", just use the distclean target: make install distclean This will clean the work directory and the distfile after installing. If you want to clean distfiles separately from installation, just run rm -rf /usr/ports/...


My copy of /usr/local/etc/pkg/repos/FreeBSD.conf read as follows in my jail: FreeBSD: { url: "pkg+", mirror_type: "srv", enabled: yes } I changed that to 10 and it worked correctly FreeBSD: { url: "pkg+


Most dependency lists are hard to parse at a glance. I prefer using this wrapper script by, because it displays a nice, nested list with both upward and downward dependencies: $ ruby18-bdb-0.6.5_1 Package ruby18-bdb-0.6.5_1 depends on: db41-4.1.25_4 ruby-,1 Package ruby18-bdb-0.6.5_1 is required by: ...


You would have to recursively get all subdependencies as well. There probably are some tools for that in the ports-mgmt category... I use portmaster(8) for port management. It always gathers (sub)dependencies before compiling and installing a port: ~> portmaster --show-work devel/apache-ant ===>>> Port directory: /usr/ports/devel/apache-ant ===&...


I don't think 4.7 is supported by the current ports tree. You might be able to edit /usr/ports/Mk/ to have a value for GCCVERSION. But considering 4.x had gcc 2.95 its likely that you will have trouble compiling unless you first upgrade gcc. Another options is to forget ports and just compile the program by hand. You can use the port Makefile ...

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