Software Station reinstalls pkgs built from ports

[youngunix]

Hello,

I use the ports to install some packages with certain configurations but the Software Station keeps reinstalling them with default config options. Is this by design?

[ericbsd]

That might be an Updated Station. Could you update the station update packages? Installing something with ports will override the package you build from ports unless you lock it. Also, if there is a specific option you want, I could ensure that it is built by default like that.

[youngunix]

This statement is confusing "Installing something with ports will override the package you build from ports unless you lock it." Do you mean, for example; if I install nano from the pkg repo (binary), it will override the one I previously built from ports (/usr/ports/editors/nano)? Regardless, I only use one method to install a pkg, either binary or ports, not both. But in this case, no one asked the Software Station to reinstall the pkg that was built from ports.

The pkgs I build from ports might have some options that I might need/want and others that I don't need/want. For example, it's not necessary for my case to build a port with NLS or Examples among other options depending on the pkg.

[repent-or-perish]

When you install software using pkg, it fetches pre-compiled binaries from the repository, configured with default options chosen by the maintainers. These may not match your specific needs.

Alternatively, compiling from the ports collection allows you to customize options such as Native Language Support and others, tailoring the software more closely to your requirements.

The warning that installing with pkg can override ports unless locked, highlights a potential conflict: pkg updates can overwrite software previously compiled from ports. To prevent this:

1. Lock: Use pkg lock to prevent automatic updates from modifying a locked package.
2. Consistency: Stick to one installation method—either ports or packages—for any given software to avoid conflicts.
3. Custom Repositories: Create and use a custom package repository with binaries built from ports with your chosen options, allowing controlled use of pkg.

If using ports for specific configurations, consider locking these installations or managing them solely through ports to maintain stability and consistency.