Date: Sat, 31 Aug 2024 10:19:28 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 249374] ports-mgmt/pkg: 1.15.4 cannot unroll hard links to copies, and still runs pkg-install after error Message-ID: <bug-249374-32340-tLTkyT30UU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-249374-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-249374-32340@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=3D249374 --- Comment #3 from Matthias Andree <mandree@FreeBSD.org> --- After receiving an email message asking what the consequence of this was, my workaround was changing the package structure and finally accepting that= I needed to copy the file. In detail, I ended up breaking up the e2fsprogs port into 1. a new e2fsprogs-core port and 2. the e2fsprogs port (the existing name) where the -core port has the stuff without links, and has the former e2fsprogs-core p= ort as a build requisite and copies two files into /sbin and packages them separately, as copies. See https://cgit.freebsd.org/ports/tree/sysutils/e2fsprogs/Makefile?id=3Dc7d90c= 65422d0b64ab00ece9237c2c4431d3ee23#n16 It isn't terribly efficient, but I could not find a better copromise that ticked all of these priority boxes: [ ] 1. not break on install when the filesystem split is different than for= the port [ ] 2. not claim checksum errors if I do things in post-install scripts [ ] 3. not create redundant copies. I did not manage to fix no. 3 with the existing pkg, and do not see how I c= an do that without assuming that there is no file system boundary between /sbin and /usr/local/whatever. --=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-249374-32340-tLTkyT30UU>