the owner of all installed files is a non-root user. This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.
(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
unprivileged.mk. These two variables are lists of other bmake
variables that define package-specific users and groups. Packages
that have user-settable variables for users and groups, e.g. apache
and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
and ${UNPRIVILEGED_GROUP}.
(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
* Client file tamper checking
* New client option 'SubmitOptions'
* Speedup of 'p4 submit' branched files
* 'Automatic' labels
* Improved management of remote depots
* New MaxLockTime in 'p4 group'
* Improved license file handling
* User file access tracking
* 'p4 integrate' improvements
* Optimization of head revision operations
* Speedup for the 'integ' command
* Early release of db.working/db.resolve during sync
* Server Performance Tracking
* Spec depot interferes less with other commands
* Special handling for @changelist
* Speedup for clients with many opened files
* External authentication triggers
* UTF-16 support
* Speedup for the 'dirs' command
* Speedup for the 'obliterate' command
* Btree passive reorganization
* MapState simplification
* Spec depot
* Partial filetypes
* Delete triggers
* Authorization and security levels
* New login/logout commands
* New trigger support
* New indirect integration default
* New smart resolve logic
* Filepaths that contain characters @#%* can be added to the depot
* New tag command provides easy way to assign a label to a filelist
* Optimization for frequent syncs
* Label use speedups
* Locking and memory use improvements
* Speedups for large client views and protections tables
* Indirect integration much faster
* New monitor command displays status of running p4 processes
* Integrate across distant branches
* New annotate command shows history of lines in a file
* Sharing clients using multiple client roots
* Sprucing up diffs
* tempobj filetype redux
* New protection level for semi-super users
and a bunch of other features and bug fixes.
backslashes anymore. A single backslash is enough. Changed the
definition in all affected packages. For those that are not caught, an
additional check is placed into bsd.pkginstall.mk.
And always is defined as share/examples/rc.d
which was the default before.
This rc.d scripts are not automatically added to PLISTs now also.
So add to each corresponding PLIST as required.
This was discussed on tech-pkg in late January and late April.
Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere
and remove the RCD_SCRIPTS_EXAMPLEDIR itself.
under share/examples/rc.d. The variable name already was named
RCD_SCRIPTS_EXAMPLEDIR.
This is from ideas from Greg Woods and others.
Also bumped PKGREVISION for all packages using RCD_SCRIPTS mechanism
(as requested by wiz).
the RCD_SCRIPTS rc.d script(s) to the PLIST.
This GENERATE_PLIST idea is part of Greg A. Woods'
PR #22954.
This helps when the RC_SCRIPTS are installed to
a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later,
the default RCD_SCRIPTS_EXAMPLEDIR will be changed
to be more clear that they are the examples.)
These patches also remove the etc/rc.d/ scripts from PLISTs
(of packages that use RCD_SCRIPTS). (This also removes
now unused references from openssh* makefiles. Note that
qmail package has not been changed yet.)
I have been doing automatic PLIST registration for RC_SCRIPTS
for over a year. Not all of these packages have been tested,
but many have been tested and used.
Somethings maybe to do:
- a few packages still manually install the rc.d scripts to
hard-coded etc/rc.d. These need to be fixed.
- maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too.
have it be automatically included by bsd.pkg.mk if USE_PKGINSTALL is set
to "YES". This enforces the requirement that bsd.pkg.install.mk be
included at the end of a package Makefile. Idea suggested by Julio M.
Merino Vidal <jmmv at menta.net>.
P4D, the Perforce Server, manages the Perforce central file repository
(the "depot"), tracks Perforce user operations, and records activity
in the Perforce SCM database. You need one Perforce Server to
support all of the users in your enterprise.
