Today I learned, or at best, relearned, a new make target: root@freshports:/usr/ports/sysutils/anvil # make create-manifest root@freshports:/usr/ports/sysutils/anvil # ls -lt | head total 14 drwxr-xr-x 3 root wheel 3 Sep 10 17:26 work -rw-r–r– 1 root wheel 337 Sep 10 16:06 pkg-descr -rw-r–r– 1 root wheel 182 Sep 10 16:06 distinfo -rw-r–r– 1 root wheel 1050 …
This post serves two goals: document the CONFLICTS implementation within FreshPorts show how you can use triggers to update a secondary table The FreeBSD ports tree / package collection has a method for resolving conflicts. This feature allows a port maintainer to specify what, if any, packages conflict with a given port. The reasons why …
Recently, I’ve been adding more and more file content into the database, mostly because it’s useful. For example, we add the contents of the distinfo, because that information is useful. Next, it was pkg-plist, and before I was done that, someone suggested added in the Makefile. Neither pkg-plist nor Makefile will be perfect: Not all …
Marie Helene asked a very good question: Does the “for run” dependency list only list direct dependencies, or depends of depends too? The answer is yes, only direct dependencies, but all the information is there to provide a complete list of all dependencies. The table looks like this: Here is the list of dependencies for …
Sir l33tname asked: @DLangille is it possible to show on freshports when there is no package for a port? — Sir l33tname (@l33tname) December 29, 2015 That’s a good question. It took some more questions on IRC for me to figure it out. Here is what I know. The port in question is net-p2p/btsync and …
FreshPorts is not magic. It grabs the stuff it needs by running make -V with a number of parameters. New fields are added from time to time, usually at the prompting of a user. Recently, the following fields were added to the dev website: FETCH_DEPENDS PATCH_DEPENDS EXTRACT_DEPENDS USES More information on these fields can be …
An interesting discussion started earlier this week: upstream dependents. At present, FreshPorts captures and displays the information output from: make -V BUILD_DEPENDS -V RUN_DEPENDS -V LIB_DEPENDS For a given port, this tells up what that port depends upon for building, running, and libraries. The request is for this same information, but in the reverse ordering; …
Two posts ago, I wrote about adding the output of showconfig to each port. I also mentioned how I should override OPTIONSFILE so FreshPorts shows the default options settings, not those particular to the FreshPorts server. Here is the output of show config for sysutils/bacula-server: $ cd /usr/ports/sysutils/bacula-server $ make show config ===> The following …
When people ask me about packages versus ports, the one main advantage of ports over packages is the ability to set the configuration options. To set the configuration options for a given port, issue this command: make config Configuration options are stored in /var/db/ports. For example, the options for sysutils/bacula-server are: $ less /var/db/ports/bacula-server/options # …
At present, master/slave relationships in FreshPorts are not stored optimally. Each port has a field, master_port, which contains the category/port of its master_port, otherwise, it is an empty string. The ideal situation would be a table such as this: create table master_slave ( master_port_id integer not null, slave_port_id integer not null, primary key (master_port_id, slave_port_id) …