Date: Sat, 29 Jul 2023 17:58:01 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 272795] FreeBSD Handbook section 4.5.1 could be better. Message-ID: <bug-272795-9-blXkV32uXm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272795-9@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272795 --- Comment #6 from Leo Bicknell <bicknell@ufp.org> --- > Maybe more relevant to focus on the version of FreeBSD. For example: I'm not sure that addresses my concern, but perhaps my concern isn't valid? The scenario I run into from time to time is: - Install everything I need from packages. - Discover 1 package was built with compile time flags different than I need. - Rebuild that singular package from ports with the changed options. What I am trying to do as a result is make sure the port I build is the "same" as the package one in terms of patches and the like. And, then when an upgrade cycle comes I generally upgrade the packages and then have to rebuild the one singular port. I feel like that might be a common scenario, but perhaps not. In any event I'm simply trying to make sure I'm all in sync, ideally programatically. In the "a sysadmin can dream" category, I would love a world where I could tell pkg "xyz from ports with options MAKEOPT=FOO" and then "pkg install" all the normal packages and have it build xyz from the ports when I tell it to install that package, and similarly do the same when I upgrade. Basically turn them into one seamless bucket of software with the ability to pick and choose in a config file which comes from where. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272795-9-blXkV32uXm>