Page MenuHomeFreeBSD

CONFLICTS_INSTALL: check later for conflicts
ClosedPublic

Authored by bapt on Aug 26 2022, 8:57 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Sep 22, 5:49 AM
Unknown Object (File)
Sat, Sep 20, 3:01 AM
Unknown Object (File)
Fri, Sep 19, 4:00 PM
Unknown Object (File)
Aug 31 2025, 3:21 PM
Unknown Object (File)
Aug 21 2025, 9:59 AM
Unknown Object (File)
Aug 6 2025, 4:16 AM
Unknown Object (File)
Jul 28 2025, 1:37 AM
Unknown Object (File)
Jul 23 2025, 3:41 AM
Subscribers

Details

Summary

Until now, the check of the CONFLICTS_INSTALL was done during the sanity
check, meaning very early in the package building process.

this makes it painful in 2 cases:

  1. a port depend at build time on the extraction of this port, it will print its warning message along with the default timer, while we will never reach the said conflict at all.
  2. since the ports tree has been staged, one can even go up to create a valid package even if a locally conflicting package is locally installed.

This change make the check and print of the conflicts only happen during the
install phase, the same way the ports tree checks if a previous version is
already installed.

PR: 213890

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable