Movatterモバイル変換

This page contains the FAQ for FreshPorts. Hopefully the questionsare arranged from general to specific. The more you know, the furtherdown you must read to find something you didn't already know.

Your primary FreshPorts tool is yourwatch list. This is thecollection of ports which you have selected for FreshPorts tokeep track of. You will be emailed when a change is foundfor one of your watched ports.

You can have more than one watch list. Most people would haveone watch list for each machine they administer. I suggest givingthe watch list the same name as the machine. Email notificationswill contain headers with the list name. You can use that for anyfiltering you may want to do (e.g. procmail).

You should be familiar with thePortssection ofThe FreeBSD Handbook.Pay careful attention to the difference between a port and a package.

Definitions for the hopelessly lazy

What is a port?

If you install the port, the source will be downloaded, patched if necessary,compiled and installed. You will have a chance to set any optional configurationitems particular to that port. If the port is dependent upon another port,that port will also be installed. After installing, ports are identical topackages.

It is because of these compile time options that I prefer ports over packages.

What is a package?

A package is a compiled port. It is a binary. When you install the package, you will download a binary and it will be installed.

Packages often lag behind ports. That is usually because it takes time to compilethe packages, etc. If you want the latest version, and the package is notavailable, then you should install the port.

Not all ports can have packages, often because of license restrictions thatprevent binary distribution.

1. Wherever you see a port, you can click on the Add () /Remove ()link as necessary (i.e. one-click watch list maintenance).
2. The 'watch list categories' link provides you with a listof categories. Select the category, and then the ports withinthat category.
3. Use the 'upload' link to upload your pkg_info data into yourwatch list staging area and then into your watch list.

One-click watch list maintenance operates only upon your defaultwatch lists. You can set one or more watch lists as being default.

git clone https://git.FreeBSD.org/ports.git /usr/ports

In the past, FreshPorts would parse the emails sent out for each commmitand then load the information into a database.In theory, it's fairly straight forward. In practice, there's much more toit than first meets the eye. The website was updated as soon as the messagearrived.

<a href="https://www.freshports.org/">FreshPorts</A>

Here is a banner which you are free to use to link to this site:

<img src="images/freshports-banner.gif" alt="FreshPorts -- The Place For Ports" title="FreshPorts -- The Place For Ports" width="468" height="60">

Please save this graphic on your website.

Homepage: a link to the Project Page / home page for this port. A port can have morethan one homepage While I personally think thedocumentation doesnot specifically allow for this, I think it arose whenWWW was moved frompkg-descrtoMakefile.

Fallout: a link to search thefreebsd-pkg-fallout archives. If the resulting fallout list is empty: the port may have been skipped due to fallout of a related port.

Repology: a link to search the Repology packaging hub for this port.

Find Bugs: a link to search for open Problem Reports (issues/bugs) for this port.

New Bug: a link to open a new Problem Reports (issue/bug) for this port.

New: This port has been recently added. A port is marked as new for 10 days.

Forbidden: The port is marked as forbidden. If you view the port details,you will see why. Most often, it is because of a security exploit. Packages for a forbidden port are not built by the package cluster. Therefore,pkg install will not work.

Broken: The port is marked as broken. Perhaps it won't compile. Maybeit doesn't work under FreeBSD right now. If you view the port details,you will see the reason why. Packages for a broken port are not built by the package cluster. Therefore,pkg install will not work.

Deprecated: The port is marked as deprecated. Perhaps it has exceededits lifetime or is obselete.

Expiration Date: The port has an expiration date. A port may be removed from the tree after this date. Often added in conjunction with Deprecated.

Expired: The port has passed the expiration date. A port may be removed from the tree after this date. Often added in conjunction with Deprecated.

Ignore: The port is marked as ignore. It probably does not build. Packages for an ignored port are not built by the package cluster. Therefore,pkg install will not work.

Files: If you click on this graphic, you will be taken to the list of filestouched by the commit in question.

Refresh: The system is in the process of refreshing that port by inspectingthe ports tree. You should rarely see this.

If you do see one, chances are that the port contains an errorthat prevents make(1) from running. For example:

$ make -V PORTVERSION
"Makefile", line 271: 1 open conditional
make: fatal errors encountered -- cannot continue

In such circumstances, the port committer is notified (if they haveopted in to the FreshPorts Sanity Check Report) and they shouldfix the problem as soon as possible. Once you see a more recentcommit without a refresh icon,then the problem has been fixed. The refresh icons will go away afterFreshPorts has dealt with the old commits. This may take a few hours.

Deleted: This port has been removed from the ports tree.

These icons for for older commits. At one time, FreshPorts parsed emails.This icon will appear alongside commits before the repo moved fromsubversion togit.They appear along side the commit message in the comit history. This link will take you to the original message in the FreeBSD mailing list archives.Note that it can take a few minutes for the message to appear in the archives. This link will not appearfor commit messages before 3 March 2002 (which is the date FreshPorts started to store the message-id).

FreshPorts commit message: This will take you to the FreshPorts commitmessage and allow you to see all other ports which were affected by this commit. This link will not appear for commit messages before 3 March 2002 (which is the date FreshPorts started to store the message-id).

NOTE: This link has been made redundant by recent advances in the Files link. See next icon.

Item is on one of your default watch lists: This port is on one of your default watch lists. Clickthis icon to remove the port from your default watch lists. This icon appears only if you are logged in.

Add item to your default watch lists: This port is not on any of your default watch lists. Clickthis icon to add the port to your default watch lists. This icon appears only if you are logged in.

Encoding Errors (not all of the commit message was ASCII): Some of thecommit message may be altered because of character conversion problems. We display only UTF-8 and removethe offending characters. These errors may occur in the log message or elsewhere in the commit email.

Watch List Count (WLC): This is the number of watch lists which are watchingthis port. This might give you an idea of the popularity of the port.

Git Repository: This link will take you to the Git Repository entryfor this version of the file.

SVN Repository: This link will take you to the Subversion Repository entryfor this version of the file.

CVS Repository: Deprecated, and historical. Probably does not appear much any more.This link will take you to the CVS Repository entryfor this version of the file. This is for much older commits.

VuXML vulnerability. Click icon for details.

A pastVuXML vulnerability. Click icon for details. NOTE: A feature of security/vuxml is it names the packages which a given vuln affects. Ifthe port changes its package name, past vulnerabilities won't show up in FreshPorts.That's because FreshPorts does not store historical package names.

This port has some restrictions on it.

This port has some restrictions with respect to being included on a CD-ROM.

This port will require interaction during installation.

Dependency Search: Action depends on context. Click on this icon to search for ports depending on thecurrent port, ports maintained by the current maintainer, or other commits by the current comitter.

Revision details. Click on the Files icon in the commit history andyou'll see what files in this port were touched by this commit. Click on the Revision details to view therevision of the file associated this commit.

Annotate: If you click on this graphic, you will be taken to a view of the file in question, with alisting of the commits that last changed each line.

Diff. Click on the Files icon in the commit history andyou'll see what files in this port were touched by this commit. Click on the Diff icon to view thediff between this revision of the file and the previous revision.

Sanity Test Failures. The maintainers and committers aregood. But sometimes a mistake slips through. This records the mistake to make it easier for others to correctit if it goes unnoticed. If you see this icon next to a commit, it failed a Sanity Test.

Flagged Commit. This commit is on your list of flaggedcommits. Why would you flag a commit? Perhaps you want to review that commit. Perhaps you want to MFC it later.Click on this icon to remove the commit from your flag list.

Click on this icon to add the commit to your flagged list.

Ascending / Descending: These icons appear on particular tables and allow changing the order rows are sorted by.

Many things changed between FP1 and FP2. The most major changewas in the underlying database schema. Not only did we movefrommySQL toPostgreSQL, we made majorchanges to the tables and the way in which the ports are storedin the database. As a result of these changes, many internal IDsand values are no longer valid. Therefore, URLs such as/port-description.php3?port=1234 no longerwork.

If it is any consolation, the new URLs are transparentand permanent. They are of the form <category>/<port>.

Yes. Readall about it!

https://www.FreshPorts.org/ is the main page of this website. It contains a lot of information. You can trim this information by using parameters.

Try this URL:https://www.FreshPorts.org/index.php?num=30&days=0

• num - number of ports to show (regardless of commits so the last commit may not list fully). The valid values are 10..100.
• days - number of summary days (in the right hand column) to display.The valid values are 0..9.
• dailysummary - similar to days, but displays a summary of the days insteadof a link to a page of commits for that day.

Description	URL
The last ten ports	https://www.FreshPorts.org/index.php?num=10
Same as above, but show only two days of previous commits	https://www.FreshPorts.org/index.php?num=10&days=2
Same as above, but show summaries instead of a link to another page	https://www.FreshPorts.org/index.php?num=10&dailysummary=2

NOTE: Effective 13 November 2003, these parameters are no longer available.

Yes, you can.https://www.FreshPorts.org/date.phpdisplays all the commits for today (relative to the current server time).

You can also pass a parameter and view the commits for a given day. For example,https://www.FreshPorts.org/date.php?date=2002/11/19will show all the commits for 19 November 2002

The date should be of the format YYYY/MM/DD but I'm sure different formatswill work. If the code has trouble figuring out what date you mean, it will guess and let you know it adjusted the date.

You have clicked on the icon and it doesn't change to a. Yes, I'vehad that happen too. What you need to do is check yourwatch list settings. You have probably selected "default watch list[s]" when you don't have any default watchlist[s] set. To mark a watch list as a default, select it in the list, then click onthe Set Default button.

NOTE: The will only appear beside a portthat is one on of your default watch lists. If the port is on one of your non-defaultwatch list, the icon will appear instead.If you do not see what you expect, try setting the default watch lists in yourwatch list settings.

Please refer to the above question.

Some ports (for examplenet/gift) will have a section titled "Port Moves".FreshPorts obtains information about ports from the commits to therepository.

Withsubversion, there could be a manual change to the repository, not creating a commit email.Such moves were often referred to as arepo-copy, and might have moved a port from one category to another.Such a change was done to ensure the port history is retained.

Withgit,repo-copies do not occur; the changes are accomplished via commits.

Such moves/commits are documented in/usr/ports/MOVED. FreshPorts parses this file and recordsthese changes in its database.

This new feature was added on 31 December 2003.

/usr/ports/UPDATING is similar to/usr/src/UPDATING, but for ports,not for the source tree.

FreshPorts parses this file and attempts to relate the entries to any portsit can find. Such relations are not always possible. We do the best we can.Thenet/openldap22-client port is a goodexample of what to expect.

Some ports are so similar to another port that it makes sense to maintain just one portand specify the differences in the other port. This is slightly similar to the way/etc/defaults/rc.conf is related to/etc/rc.conf.

A good example iswww/mod_php4. You can see that themaster port for that islang/php4.Conversely,lang/php4 lists severalslave ports.

The ability to add this feature is because of this patch:

--- bsd.port.mk10 Jun 2004 07:30:19 -00001.491+++ bsd.port.mk22 Jun 2004 13:48:33 -0000@@ -913,6 +913,16 @@  MASTERDIR?=${.CURDIR} +# Try to determine if we are a slave port.  These variables are used by+# FreshPorts and portsmon, but not yet by the ports framework itself.+.if ${MASTERDIR} != ${.CURDIR}+IS_SLAVE_PORT?=yes+MASTERPORT?=${MASTERDIR:C/[^\/]+\/\.\.\///:C/[^\/]+\/\.\.\///:C/^.*\/([^\/]+\/[^\/]+)$/\\1/}+.else+IS_SLAVE_PORT?=no+MASTERPORT?=+.endif+ # If they exist, include Makefile.inc, then architecture/operating # system specific Makefiles, then local Makefile.local.

The FreeBSD tree has no defined method for handling master/slave ports.It is because of this that FreshPorts never attempted to refresh slave portswhen a master port was updated. Now that we have a mostly-reliable method,all slave ports are refreshed when the master port is updated.

This method works for all but 40 ports which are involved in a master/slave relationship.It is hoped that those 40 are fixed soon. It is also hoped that the above patchis comitted to the tree.

Included within the port description is the instruction for adding the package.This information can be important when the package name does not match theport name. A good example isx11/XFree86-4-clients.The command to add this package is:

pkg install XFree86-clients

This normally isn't a problem, but for the 1900 or so ports which are different,this information is very useful.

If thepkg install information does not appear,you'll be told why there is no package. This is controlled by theNO_PACKAGE variable in the port's Makefile.

Broken, ignored, and forbidden ports are not built by the packagecluster. Therefore, there is no package forpkg install to use.

If you visit thesearch page, and you run a search,you'll find that the URL becomes very long. For example,this really long link.

Long URLs occur like that because the search form uses a GET. A long URLwould not occur if it was using a POST. The long URLs are useful becausethey allow you to bookmark your favorite search. That is why a GET is usedinstead of a POST.

It also makes it easier tovalidate the HTMLif you can provide a URL that exercises all the options that require testing.

For those familiar with the FreeBSD ports structure, the following fields indicate their origin:

$ cd /usr/ports/sysutils/bacula/
$ make -V PORTNAME
bacula
$

Like many FreshPorts features, this idea came from someone else. Florent Thoumie mentioned something about extending the ports system to include recommendations from maintainers/committers. Such a feature would allowa committer/maintainer to suggest, for example, that if you install Firefox,that you also install linuxflashplugin.

It was from this concept that I came up with "People watching this port...".This information is obtained by:

1. FreshPorts takes the port you are looking at
2. It finds all the watch lists that this port appears on
3. It finds the top 5 most popular ports on those lists
4. FreshPorts shows you the results

All of this takes about 55ms.

For some slave ports, you may see a message like this, just above theCommit History:

NOTE: This slave port may no longer be vulnerable to issues shown below because the master port has been updated.

Slave ports can be updated with a commit against the master port. A commitagainst the master port will affect any slave ports. If aVuXML vulnerability has been recordedagainst a slave port, any fix would be applied to the master port.However, the commit to the master port would not appear under the slave port,thereby giving a false impressionthat the slave port was still vulnerable.

The above notice serves as a reminder that the slave port may no longer be vulnerable.

Each port displays the master sites from which its distfiles can be downloaded. Thisinformation is obtained from "make master-sites-all". However, this is not the onlylist of master sites that a port knows about. Edwin Groothuis explains it in thisemail.

In short, FreshPorts displays the list of master sites that should contain allthe distfiles. That is why we use that value, and not one of the other options.

FreshPorts used to obscure email addresses, but we don't any more. We realised thatevery email address on FreshPorts is already somewhere else first. For example:

• www/ports pages
• portsmon
• fenner's output
• GNATS
• cvsweb (now deprecated)
• subversion (still online, but replaced bygit)
• git

In short, it doesn't make sense to obscure that which is freely available elsewhere.

Similarly, we do not entertain requests to remove information from our website. We only report upon what exists elsewhere.

This question refers to a port page.

This situation usually occurs with MASTER/SLAVE ports. The Master port is updated with a newREVISION. No commit is done against the Slave port. FreshPorts knows to refresh the Slave portwhen its Master port is updated. This refresh updates the PORTVERSION at the top of the page. This update reflects the REVISION you would get if you were to install the Slave portnow that the Master has been upgraded.

Anchors in port pages include:

• description
• man
• add
• flavors
• distinfo
• packages
• masterport
• slaveports
• pkg-plist
• dependencies
• requiredbuild
• requiredtest
• requiredrun
• requiredlib
• requiredfetch
• requiredpatch
• requiredextract
• requiredby
• RequiredByBuild
• RequiredByExtract
• RequiredByFetch
• RequiredByLibraries
• RequiredByPatch
• RequiredByRun
• requiredfor
• conflicts
• config
• options
• uses
• sites
• message
• updating
• history

Anchors make it easier to link to sections within pages.

For example, this link – note the#history at its tail – takes you to the commit history for security/acme.sh:

security/acme.sh/#history

Browser extensions such asDisplay #Anchors andAnchors Reveal can help to visualise anchors that would otherwise be invisible.

Enjoy. We can add more anchors upon request.

Yes, yes, you can.

Not only can FreshPorts email you when one of your watched ports is updated, it can also email you when the package is ready to install.

FreshPorts polls the available FreeBSD repo builds on an hourly basis. It uses that information to display the packages available under various ABI (e.g. FreeBSD:14:amd64). NOTE: we do not display packages for the quarterly branch on the latest CURRENT of FreeBSD. Packages are not build for that ABI/package set combination. You may see CURRENT/quarterly listed on some pages. That is easier to do than to keep track of which branch is CURRENT.

To get new package notifications, follow these steps:

1. Click onReport Subscriptions, underWatch Lists in the right hand column
2. Check theNew Package Notification box
3. click on Update
4. Again underWatch Lists, this time, click onABI Package Subscriptions to select the ABI for which you want to receive notifications
5. On this page, select one or more items from each of the first three boxes:
   1. watch lists (first box)
   2. ABI (second box)
   3. one or both of quaterly and latest (third/ box)
   and click onAdd

When the next updates arrive, you'll get an email.

FreshPorts covers the ABIs published athttps://pkg.freebsd.org/index.html.

In general, the FreeBSD Project does not build quarterly branches for whatever branch is CURRENT.

At the time of writing (2024-08-24), the code to extract those ABIs and the current ABI list was:

[15:25 dvl-ingress01 dvl ~/scripts] % cat ./current-list-of-valid-abi.sh#!/bin/shfetch -qo - https://pkg.freebsd.org/index.html | \  grep FreeBSD: | sed -e 's@.*\(FreeBSD:[^ <]*\).*@\1@' | sort[15:25 dvl-ingress01 dvl ~/scripts] % sh ./current-list-of-valid-abi.sh FreeBSD:13:aarch64FreeBSD:13:amd64FreeBSD:13:armv6FreeBSD:13:armv7FreeBSD:13:i386FreeBSD:13:powerpcFreeBSD:13:powerpc64FreeBSD:13:powerpc64leFreeBSD:14:aarch64FreeBSD:14:amd64FreeBSD:14:armv6FreeBSD:14:armv7FreeBSD:14:i386FreeBSD:14:powerpcFreeBSD:14:powerpc64FreeBSD:14:powerpc64leFreeBSD:15:aarch64FreeBSD:15:amd64FreeBSD:15:armv7FreeBSD:15:powerpcFreeBSD:15:powerpc64FreeBSD:15:powerpc64le

11 vulnerabilities affecting 299 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last processed:
2025-04-02 19:38:06 UTC