Date: Sat, 20 Aug 2022 16:33:16 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 265651] [NEW PORT] archivers/zpaqfranz: versioned/snapshot archive Message-ID: <bug-265651-7788-pgJyZOdnUg@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265651-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-265651-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265651 --- Comment #21 from Felix Palmen <zirias@freebsd.org> --- (In reply to Franco Corbelli from comment #20) > If static linking is not allowed on FreeBSD, then let it be dynamic It's not forbidden, but it's typically removed if there is no unavoidable reason. Remember, we're talking about managed packages here. No way required libs will just disappear (except for a user going rogue as root, but that's= not really a concern). In your case, you're only linking libraries from base. T= hose are guaranteed to never receive incompatible changes (but they *might* rece= ive security updates). Linking them statically will have two undesirable effect= s: - you can't control whether security fixes are really applied - you lose reproducible builds when these libs are ever changed So, in this case here, I see no reason for static linking. It's a different story if you want to provide a "portable" binary outside of FreeBSD ports as some kind of rescue tool, there, static linking makes a lot of sense. > I will make another one, almost identical, where the executable will be c= alled > just... dir Almost certainly, this wouldn't be accepted, and people would tell you "add= a symlink to your original port". > Because it happens to remove the executable of zpaqfranz, keeping the one= of > dir. No, this certainly doesn't happen when both are in the same package. Again,= a root user "going rogue" is not a relevant scenario. > When there is a (backup) program update "you" can't just change the execu= table > and that's it, from version 5.3 to 5.4. >=20 > You will need to keep at least two different program versions (the old an= d the > new) and two different backup archives (the old and the new) > [=E2=80=A6] This sounds like a port/package would be unsuitable for your software. Ther= e's no sane way to keep multiple versions installed. You would have to create a= new port for each and every version if that is *really* needed :o Multiple ports can be a strategy (there are ports doing that), but not if e= very single version drops backwards compatibility ... it can't grow forever. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265651-7788-pgJyZOdnUg>