Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing on
one package, a plugin for bitlbee, however I’d like to extend my hand to
maintain other ports in the future once I have more knowledge and practice with
the system.
Before I start, though, I just need some clarifica
On 13/12/2018 14:41, Arthur Pirika wrote:
1. If I understand correctly, the version of the ports tree as fetched by
portsnap isn’t the best for working on the tree. I should instead make another
copy of the tree as an svn checkout? Distfiles, however, still go to
/usr/ports/distfiles
If you'
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote:
> Hi all! I’m hoping to get into porting for FreeBSD, right now just
> focusing on one package, a plugin for bitlbee, however I’d like to
> extend my hand to maintain other ports in the future once I have more
> knowledge and practice w
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote:
> Hi all! I’m hoping to get into porting for FreeBSD, right now just focusing
> on one package, a plugin for bitlbee, however I’d like to extend my hand to
> maintain other ports in the future once I have more knowledge and practice
On 12/13/18 10:06 AM, Matthew Seaman wrote:
> [...] So long as you have sufficient disk space
> and you aren't trying to rebuild the entire ports tree, it can work well
> on a very ordinary desktop machine. [...]
Still getting used to the idea that a machine with >16GB would today
be considered a
On Thu, Dec 13, 2018 at 11:00 AM George Mitchell wrote:
>
> On 12/13/18 10:06 AM, Matthew Seaman wrote:
> > [...] So long as you have sufficient disk space
> > and you aren't trying to rebuild the entire ports tree, it can work well
> > on a very ordinary desktop machine. [...]
>
> Still getting u
On 14/12/2018 2:11 am, Lars Engels wrote:
On Thu, Dec 13, 2018 at 10:41:01PM +0800, Arthur Pirika wrote:
Hi all! I’m hoping to get into porting for FreeBSD, right now just
focusing on one package, a plugin for bitlbee, however I’d like to
extend my hand to maintain other ports in the future once
On 14/12/2018 7:09 pm, Kubilay Kocak wrote:
While special targets (check-plist) can be and are useful, the only form
of QA we should be doing is 'all of it', and at the present moment, that
is:
1) portlint -AC (or better)
2) poudriere testport (supported versions/archs, at least tier1 [1]
