dhcp

Overview

dhcp packages the ISC DHCP software from Internet Systems Consortium (ISC). ISC describes it as a complete open source solution for DHCP servers, relay agents, and clients. DHCP is used to assign IP addresses and provide basic network configuration to hosts on an IP network. ISC also states that ISC DHCP reached end of maintenance in 2022, so NiceOS maintainers should treat upstream status as EOL and verify current packaging needs before making assumptions about future fixes or behavior. (isc.org)

Purpose and typical use cases

This package exists so a Linux distribution can provide software for networks that still rely on ISC DHCP behavior, configuration files, and operational workflows. Typical use cases include:

• running a DHCP server for IPv4 or IPv6 address assignment and basic network configuration,
• relaying DHCP traffic between network segments,
• testing or maintaining legacy deployments that already use ISC DHCP conventions,
• supporting operators who need a packaged copy of the upstream tools for inspection, migration, or compatibility work. (isc.org)

Typical users are network administrators, system administrators, CI/CD or build maintainers who package or rebuild the RPM, and engineers who maintain legacy network automation or migration paths. NiceOS maintainers should verify whether the package is still needed in their target environments, since ISC recommends newer deployments consider Kea DHCP instead. (isc.org)

Upstream project

Upstream is ISC DHCP from ISC. ISC’s current site describes the project as open source DHCP server, relay agent, and client software, and notes that it is no longer maintained. The upstream documentation and manual pages are still useful as references for behavior, configuration syntax, and migration planning, but maintainers should verify any operational detail against the exact source shipped in NiceOS. (isc.org)

Canonical upstream references:

• project page and status information on ISC’s site,
• ISC DHCP manual pages,
• ISC download page and release notes information. (isc.org)

Dist-git repository contents

This dist-git repository is organized as follows:

• SPECS/ — RPM spec files and related packaging logic,
• SOURCES/ — source integrity metadata and manifests used by the build system,
• METADATA/ — repository metadata maintained by the packaging workflow,
• SBOM/ — software bill of materials material, when present in the package workflow.

Large upstream source archives are intentionally not stored in this Git repository. Instead, the repository keeps source-manifest information in SOURCES/ so the package can be rebuilt from tracked metadata without carrying the full upstream payload in Git. (isc.org)

Source storage and integrity policy

NiceOS tracks source integrity through the manifest files stored in SOURCES/. The repository should contain the metadata needed to identify the expected upstream source content, while the large source archive itself remains outside the Git history. Maintainers should review the manifests whenever sources are refreshed and confirm that the recorded source set still matches the intended upstream release and packaging policy. (isc.org)

Because this project is upstream EOL, any source update, patch refresh, or backport should be treated carefully. NiceOS maintainers should verify whether the change is necessary, whether it is already covered by the distribution’s own patches, and whether the expected behavior still matches local network deployment needs. (isc.org)

NiceOS maintenance notes

Before updating this package, NiceOS maintainers should check:

• whether the update is still justified for a deprecated upstream project,
• whether any downstream patches still apply cleanly,
• whether any spec conditionals, scriptlets, or file lists need adjustment,
• whether generated packaging files or source manifests in SOURCES/ need regeneration,
• whether SBOM/ material needs to be refreshed to reflect the new package contents,
• whether the update changes runtime paths, service files, or configuration file handling,
• whether migration guidance is needed for users moving away from ISC DHCP. (isc.org)

Practical risks to consider:

• upstream no longer publishes maintenance releases,
• behavior changes may affect existing DHCP leases or configuration files,
• legacy deployments may depend on exact command-line or config-file semantics,
• package updates may be unnecessary if the distribution is only preserving compatibility. (isc.org)

Build and verification checklist

For RPM maintenance and rebuilds, check the following:

1. Confirm the source manifests in SOURCES/ match the intended upstream content.
2. Review the spec file for patch applicability and build-time conditionals.
3. Run the package build in a clean environment.
4. Inspect build logs for warnings, missing files, or changed installation paths.
5. Verify the installed files and ownership rules against the spec.
6. If the package ships services or helpers, confirm they start, stop, and reload as expected in a test environment.
7. Test the relevant DHCP server or client workflows used by your packaging scope.
8. Check that documentation, license files, and SBOM material remain consistent with the packaged sources.
9. For updates, compare configuration and runtime behavior with the previous packaged version before publishing. (isc.org)

References

• ISC DHCP project page
• ISC downloads page
• ISC DHCP manual pages: dhcpd
• ISC source access page
• ISC Kea DHCP project page

Russian documentation

See README_RU.md for the Russian version of this document.

Dist-git repository notes

• Package repository: rpms/dhcp
• NiceOS branch: niceos-5.2
• This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.