Date: Sun, 13 Nov 2022 22:15:01 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 267717] Resurrect devel/root Message-ID: <bug-267717-7788-IR6MpvEeFK@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267717-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-267717-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=3D267717 --- Comment #6 from Erik Jensen <erik@tenku.dk> --- Comment #1, comment #5 - thank you very much for your helpful replies, Chri= s! I have changed the title of the port. Do you prefer to keep the port in the =E2=80=9Cdevel=E2=80=9D category? I p= ersonally think it=20 would fit a bit better in the =E2=80=9Cscience=E2=80=9D category, but my op= inions in this regard=20 are neither super strong nor pulling on much more than a few months of experience=20 with FreeBSD ports. I can also see a couple of arguments against naming the port the (in my opinion, very poorly chosen) name of the software =E2=80=9Croot=E2=80=9D, but this i= s what the original=20 authors have decided upon, so I initially chose this name for the port.=20 The official GitHub project has this name for the code repository as well.= =20 Do you, anyway, think a port name such as =E2=80=9Ccernroot=E2=80=9D would = be better, so as not=20 to confuse the port for a sysadmin account and similar? I think I have managed to prepare the port. I have been running a testport on my specifications in a poudriere jail, but compiling gcc11 (a prerequisi= te=20 for some of the python dependencies, I believe; ROOT itself is compiled wit= h=20 llvm/clang) on my current limited capacity system hit the default timeout o= f 24=20 hours! I see in the documentation that there are several ways to get around this. Anyway, in not too long I=E2=80=99m hoping to be able to upload the port he= re.=20 Thanks again --=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-267717-7788-IR6MpvEeFK>