|Summary:||[new port] x11-wm/Motif|
|Product:||Ports & Packages||Reporter:||John Hendrickson <johndhend>|
|Component:||Individual Port(s)||Assignee:||freebsd-ports-bugs (Nobody) <ports-bugs>|
|Severity:||Affects Some People||CC:||swills|
Description John Hendrickson 2021-02-26 23:01:04 UTC
https://github.com/johndhend/Motif I belive is ready to become a NEW port. I ask for advice on "what would be best for the port team" or for them to add it into upcoming release intitially so I can work from that point on (responding to complaints before release). The handbook asks I not "submitt a whole tarball as an svn .diff" to bugzilla (and a diff cannot be made because x11-wm/Motif does not exist). POINT: it is not even thinkable as a .diff to redhat motif - this is for freeBSD, not a linux port. WHY: Motif (motif-2.5.0) is a pure freeBSD compile (amd64/any) of ~ 2.2.3 with many things fixed still broken in x11-toolkits/openmotif-2.3.8 by redhat (which is autoconf and doesn't compile correcly like it says it does, is controlled by redhat not freeBSD, breaks imake other dire things, requires GNU new depends 2.5.0 has 0). Made my POINT: way different. The source, NEWS, pkg-descr is on github, I won't jam you with advertising here. NEW PORT ERRATA: I could but do not asks for gpg key and mentor rights to alter the svn tree to add a node or for svn up submittal. I don't want to be more complicated than the ports team have request me to be. I want to keep it simple. This is my very first freebsd bugzilla posting. I may not know all the rules yet. Thanks sorry for boring you with details if I did!
Comment 1 Steve Wills 2021-02-26 23:23:18 UTC
Is this different from x11-toolkits/open-motif ?
Comment 2 Mark Linimon 2021-02-27 01:05:11 UTC
(In reply to John Hendrickson from comment #0) With respect to commit rights, here are the documents you should read first: https://docs.freebsd.org/en_US.ISO8859-1/articles/contributing/ports-contributing.html https://www.freebsd.org/portmgr/policies/ (under "Manage Commit Access To The Ports Tree") Thanks.
Comment 3 John Hendrickson 2021-02-27 01:14:59 UTC
(In reply to Steve Wills from comment #1) I was very clear they are absolutely different and the github post makes that un-arguable.
Comment 4 John Hendrickson 2021-02-27 01:18:26 UTC
(In reply to Mark Linimon from comment #2) So your lead is "WHEN TO ADOPT A PORT WHEN TO CALL IT QUITS" and ... "WHY MAINTAIERS ARE YOUR GOD"? I'm not "adopting red hat and their attempt to be free software leach king". That's not how this is going to work. They broke motif to fit their system of forced upgrades and platform dependence upon RH and UBUNTU. I'M VERY MUCH AWARE some ubuntu admins slipped over to freeBSD as soon as people began seeking to get out of Ubuntu - frustrated with the admins. By the way.
Comment 5 Mark Linimon 2021-02-27 06:26:59 UTC
(In reply to John Hendrickson from comment #4) I thought you were asking about FreeBSD commit rights. Some people do not know how we allow access to the repos. So I thought I would quickly quote the relevant articles. I apologize for not reading more carefully. As for Ubuntu and RedHat, I have no idea what goes on in their communities. I have been working exclusively on FreeBSD for years. So I have no idea what the relevance to these comments are.
Comment 6 Chris Hutchinson 2021-03-01 22:46:46 UTC
If I understood your question correctly. To create/submit a new port. You can attach it as a shar(1) file. eg; $ shar `find port-name` > portname.shar I know it's *somewhere* in the porters handbook. But I think just knowing the basic command should be evidence enough for you to understand what's required. :-) Good luck! --Chris