On FreeBSD I sometimes update my software packages using ports and that overwrites what DirectAdmin installed using CustomBuild with newer versions. That way I end up with notices when doing ./build versions similar to those:
I don't mind about seeing the messages themselves - it is GOOD to know that what I use is not what DA provides!
What bothers me is that I can no longer do ./build update_versions because that will downgrade my packages and unsync it with the latest ports versions again.
Could you think up of an alternative way to perform update_versions in a way that it should not downgrade unless you add an additional "force" option or something like that? Or, to keep backwards compatibility, add a new option like ./build update_versions_with_no_downgrades?
I don't mind about seeing the messages themselves - it is GOOD to know that what I use is not what DA provides!
What bothers me is that I can no longer do ./build update_versions because that will downgrade my packages and unsync it with the latest ports versions again.
Could you think up of an alternative way to perform update_versions in a way that it should not downgrade unless you add an additional "force" option or something like that? Or, to keep backwards compatibility, add a new option like ./build update_versions_with_no_downgrades?
Last edited:
