On 2021/05/24 18:10, Stephane Guedon wrote: > Le lundi 24 mai 2021, 16:59:15 CEST Stuart Henderson a écrit : > > On 2021/05/24 15:25, Stephane Guedon wrote: > > > Hello > > > > > > I am beginning to write a peertube port, just as a way to better > > > manage my instance. I don't know if it will succeed. > > > > > > PeerTube uses nodejs and requires having the node binary in /tmp to > > > build its modules. Is there a way to deal with that or should I > > > write a "pre-build" target to copy/link node in the chroot phase ? > > > > > > (I hope I understood the building process fine and that I make > > > myself > > > understood ok too.) > > > > > > Thanks for help > > > > It's not going to work, you can't rely on /tmp being mounted with > > "wxallowed". > > Shouldn't the actual tmp repository being used during building be in > /usr/obj/ports/portname/something/tmp ... ? meaning in the /usr > partition, where it is normally allowed ? > > >
Port build directories themselves can be expected to have wxallowed, but that doesn't fit with your software which requires the node binary in /tmp. (that seems a strange requirement in the first place; it's not all that uncommon to mount /tmp "noexec" even). Between this, and common requirement that dependencies are fetched with yarn/npm at build time (which is not permitted in ports; only the ports infrastructure itself may fetch from the network, the build process itself must only use files from disk), software written in node is not usually a viable candidate for adding to ports.
