On 10/27/22 02:53, Pavel Korovin wrote: > On 10/26, A Tammy wrote: >> Wanted to revisit this. >> >> I'm for the split, as it is going to give a seamless upgrade. >> I've got multiple ansible controlled boxes, I'd prefer not having to >> manually handle stuff. > Hi Aisha, > > I'm against the split because I don't see real deal having the bare gitea > package and gitea-web part. I don't like Linux approach with *-libs > *-devel *-includes *-docs *-whatever packages, for me it looks like making > complexity out of nothing. The only reason I see for the split could be > seamless upgrade, if it's really possible with the package split, > but I'm not sure about the seamlessness of the upgrade. > > I tried building gitea with PREFIX="/" trick, and it worked almost fine, > but then figured out that it breaks sysutils/sysclean (sysclean just hangs > when gitea is installed). > Currently I use @cwd approach recommended by Stuart, but it requires manual > intervention during the port upgrade (the diff for latest gitea-1.17.3 is > attached). > > I'd vote for upgrade with manual intervention accompanied by an entry in > current.html. My Gitea upgrade process includes at least 1 manual step > (DB backup), so from my experience it doesn't hurt to pkg_delete port > and pkg_add port instead of doing pkg_add -u. > I guess I can agree with this reasoning, so might as well rip off the bandaid :D
Aisha
