Hi all,
I was initially involved in updating a port without maintainer
(multimedia/ffmpegthumbnailer), which was taken over by someone else.
I'm just starting out with porting and have updated several outdated
ones already. So that's fine.
What irritates me however, is the conflicting inform
Thanks for the link, I have read it with great interest. The conclusion
is supporting the interpretation that a porter should always use the
release tarball if one is available. Makes a lot of sense to me. This
should be stated more clearly in the Porter's Handbook with a sentence
or two to tha
Firefox has Rust as a dependency. In the past I have found that the build
process for the latter easily overwhelms lean systems with little physical RAM.
Regardless of swap space, quite unlike most other ports.
Marcel
On 30 Aug 2020, at 17:49, bob prohaska wrote:
> Apologies, the port in quest
