FreeBSD Cert

Brandon helsley brandon.helsley at hotmail.com
Wed May 27 16:41:53 UTC 2020


Ok I'll check it out and get back to you. Btw there's a broken port called freetnet. Can it be rescued? How do you go about fixing a broken port?
________________________________
From: Aryeh Friedman <aryeh.friedman at gmail.com>
Sent: Wednesday, May 27, 2020 10:38:56 AM
To: Brandon helsley <brandon.helsley at hotmail.com>
Cc: Ottavio Caruso <ottavio2006-usenet2012 at yahoo.com>; Polytropon <freebsd at edvax.de>; Ottavio Caruso via freebsd-questions <freebsd-questions at freebsd.org>
Subject: Re: FreeBSD Cert



On Wed, May 27, 2020 at 12:35 PM Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>> wrote:
So if I wanted to port Bote Mail from i2p I would just get the source code and refer to their licensing on their website and contact them for clarity?

You should also read the semi official statement on what is compatible and what isn't legally (I am not going to summerize it because that is where the flamewar on licensing often starts): https://www.freebsd.org/doc/en_US.ISO8859-1/articles/bsdl-gpl/index.html



Sent from Outlook Mobile<https://aka.ms/blhgte>

________________________________
From: Aryeh Friedman <aryeh.friedman at gmail.com<mailto:aryeh.friedman at gmail.com>>
Sent: Wednesday, May 27, 2020 10:07:29 AM
To: Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>>
Cc: Ottavio Caruso <ottavio2006-usenet2012 at yahoo.com<mailto:ottavio2006-usenet2012 at yahoo.com>>; Polytropon <freebsd at edvax.de<mailto:freebsd at edvax.de>>; Ottavio Caruso via freebsd-questions <freebsd-questions at freebsd.org<mailto:freebsd-questions at freebsd.org>>
Subject: Re: FreeBSD Cert



On Wed, May 27, 2020 at 12:02 PM Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>> wrote:
I'll take that to mean that I can sign up with as little as I know. I'll definitely be very quick to learn. How can I get started?

Step 1: Find some program that you think should be widely available to the FreeBSD community
Step 2: Make sure it legally compatible with FreeBSD and it's licensing model (I am not going to get into how to this to avoid starting a flame war)
Step 3: Get the source code for the program
Step 4: Using hand compiling (or how ever it wants to be built) get it to compile/install cleanly including noting all the other ports it depends on
Step 5: Use the port system to automate step 4
Step 6: Submit it to the bug tracking system as a new port so as to mark it ready for a committer to review and commit it
Step 7: Make any changes the committer suggests
Step 8: Committer commits it and it is now officially a port
________________________________
From: Aryeh Friedman <aryeh.friedman at gmail.com<mailto:aryeh.friedman at gmail.com>>
Sent: Wednesday, May 27, 2020 9:57:30 AM
To: Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>>
Cc: Ottavio Caruso <ottavio2006-usenet2012 at yahoo.com<mailto:ottavio2006-usenet2012 at yahoo.com>>; Polytropon <freebsd at edvax.de<mailto:freebsd at edvax.de>>; Ottavio Caruso via freebsd-questions <freebsd-questions at freebsd.org<mailto:freebsd-questions at freebsd.org>>
Subject: Re: FreeBSD Cert



On Wed, May 27, 2020 at 11:53 AM Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>> wrote:
Good to know, then I'll take it up to learn the basics. And to be a committer? Does that require skills?

1. The reason I suggested some of the things I have written but not made into ports yet is I wrote them on FreeBSD so there is little or no programming required to make them work as  port (if there is then I did my job wrong) and thus you can learn porting from the ground up and then move to harder things that require programming

2. Being a committer is mostly being trusted by other committers to not <bleep> things up when you put it in the master repository.   Mostly this comes from maintaining a lot of ports and showing superior knowledge of the porting system along with being suitably risk adverse when updating the master repo.


Sent from Outlook Mobile<https://aka.ms/blhgte>

________________________________
From: Aryeh Friedman <aryeh.friedman at gmail.com<mailto:aryeh.friedman at gmail.com>>
Sent: Wednesday, May 27, 2020 9:48:39 AM
To: Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>>
Cc: Ottavio Caruso <ottavio2006-usenet2012 at yahoo.com<mailto:ottavio2006-usenet2012 at yahoo.com>>; Polytropon <freebsd at edvax.de<mailto:freebsd at edvax.de>>; Ottavio Caruso via freebsd-questions <freebsd-questions at freebsd.org<mailto:freebsd-questions at freebsd.org>>
Subject: Re: FreeBSD Cert



On Wed, May 27, 2020 at 11:36 AM Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>> wrote:
How much experience is necessarry?
I don't know anything about computers but got freebsd as a project to learn as much as possible. If I were to get involved does "teaching the ropes" at all possibly include learning other things like networking and possibly and hopefully learning how to port software?

A lot of times (but by far from all the time) porting requires at least basic programming skills since you often need to find parts of the code that are incompatible with FreeBSD and make them compatible (you then include a patch for the work in the port files).



Sent from Outlook Mobile<https://aka.ms/blhgte>

________________________________
From: Aryeh Friedman <aryeh.friedman at gmail.com<mailto:aryeh.friedman at gmail.com>>
Sent: Wednesday, May 27, 2020 8:33:10 AM
To: Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>>
Cc: Ottavio Caruso <ottavio2006-usenet2012 at yahoo.com<mailto:ottavio2006-usenet2012 at yahoo.com>>; Polytropon <freebsd at edvax.de<mailto:freebsd at edvax.de>>; Ottavio Caruso via freebsd-questions <freebsd-questions at freebsd.org<mailto:freebsd-questions at freebsd.org>>
Subject: Re: FreeBSD Cert



On Wed, May 27, 2020 at 8:39 AM Brandon helsley <brandon.helsley at hotmail.com<mailto:brandon.helsley at hotmail.com>> wrote:
What about port maintainership. Or port mentee? What Is it exactly. Good learning experience?

Yes/no/maybe is it worth and is it a good learning experience.

A port maintainer as Mathew said is resonible for keeping a port in good working order visa vie FreeBSD.  A good example is when I took over maintainership of devel/aegis it was to update to the latest released version (the original author passed away in 2014 and no one has picked up the ball to make new versions since despite a small group of hardcore users [including my self]) and all was good then when FreeBSD started to phase out the preference for GCC I had to make some patches to make it work with LLVM, etc.

Taking over a dead port is likely not as good of an learning experience as making and maintaining a new one.   Contact me privately I have some ideas for stuff that can and should be ports that I haven't had time for (mostly side projects relating to PetiteCloud that I can maintain via aegis but not via ports due to not making the translation scripts completely yet)
--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


More information about the freebsd-questions mailing list