FreeBSD ports tree (read-only mirror)
e761728685
* Add Long Term Support release of ClamAV * Add CONFLICTS_INSTALL to security/clamav * Add entry to UPDATING that explains - Upstream changed their end-of-life policy and LTS release is introduced - How to switch from regular release (security/clamav) to LTS release (security/clamav-lts) Note about setting PORTEPOCH In general new port should not set PORTEPOCH. But in this case it should be set with following reason. 1. Recently upstream changed their end-of-life policy as following. - Regular feature release (= 0.xyz.0 release) is released more frequently, and life time of each feature release is shortened to about 4 months. - To compensate for the short lifetime of regular feature release, Long Term Support feature release is introduced and its life time is about 3 years. 2. First LTS starts with version 0.103.3 and it is same as current version of security/clamav. 3. Because of short lifetime of regular feature release, it is probable that not a few users of security/clamav want to switch to security/clamav-lts after the latter is connected (and the former is updated to 0.104.0). 3. For such users the entry is added to UPDATING about how to switch from security/clamav to security/clamav-lts. And binary package user is suggested to execute `pkg set -o security/clamav:security/clamav-lts`. This command changes the origin of already installed clamav packages. So user can switch to LTS version without reinstalling. 4. But if PORTEPOCH isn't set in security/clamav-lts, binary package user who executed above command will notice that version of installed package (0.103.3,1) succeeds to current version of security/clamav-lts (0.103.3). The situation doesn't change after new patch release (0.103.4 for example) is released and it causes the problem that installed package isn't properly upgraded with `pkg upgrade`. 5. So PORTEPOCH is set in security/clamav-lts to prevent binary package user from suffering from such problem. |
||
---|---|---|
.hooks | ||
accessibility | ||
arabic | ||
archivers | ||
astro | ||
audio | ||
base | ||
benchmarks | ||
biology | ||
cad | ||
chinese | ||
comms | ||
converters | ||
databases | ||
deskutils | ||
devel | ||
dns | ||
editors | ||
emulators | ||
finance | ||
french | ||
ftp | ||
games | ||
german | ||
graphics | ||
hebrew | ||
hungarian | ||
irc | ||
japanese | ||
java | ||
Keywords | ||
korean | ||
lang | ||
math | ||
misc | ||
Mk | ||
multimedia | ||
net | ||
net-im | ||
net-mgmt | ||
net-p2p | ||
news | ||
polish | ||
ports-mgmt | ||
portuguese | ||
russian | ||
science | ||
security | ||
shells | ||
sysutils | ||
Templates | ||
textproc | ||
Tools | ||
ukrainian | ||
vietnamese | ||
www | ||
x11 | ||
x11-clocks | ||
x11-drivers | ||
x11-fm | ||
x11-fonts | ||
x11-servers | ||
x11-themes | ||
x11-toolkits | ||
x11-wm | ||
.arcconfig | ||
.gitignore | ||
CHANGES | ||
CONTRIBUTING.md | ||
COPYRIGHT | ||
GIDs | ||
Makefile | ||
MOVED | ||
README | ||
UIDs | ||
UPDATING |
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: https://www.FreeBSD.org/ports For general information on the Ports Collection, please see the FreeBSD Handbook ports section which is available from: https://docs.freebsd.org/en/books/handbook/ports/ for the latest official version or: The ports(7) manual page (man ports). These will explain how to use ports and packages. If you would like to search for a port, you can do so easily by saying (in /usr/ports): make search name="<name>" or: make search key="<keyword>" which will generate a list of all ports matching <name> or <keyword>. make search also supports wildcards, such as: make search name="gtk*" For information about contributing to FreeBSD ports, please see the Porter's Handbook, available at: https://docs.freebsd.org/en/books/porters-handbook/ NOTE: This tree will GROW significantly in size during normal usage! The distribution tar files can and do accumulate in /usr/ports/distfiles, and the individual ports will also use up lots of space in their work subdirectories unless you remember to "make clean" after you're done building a given port. /usr/ports/distfiles can also be periodically cleaned without ill-effect.