Bug 256452 - [new port] net-mgmt/unbound-telemetry - replacement for net-mgmt/unbound_exporter
Summary: [new port] net-mgmt/unbound-telemetry - replacement for net-mgmt/unbound_expo...
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-06-06 19:08 UTC by paul
Modified: 2021-06-07 16:57 UTC (History)
1 user (show)

See Also:


Attachments
contents of net-mgmt/unbound-telemetry (26.19 KB, text/plain)
2021-06-06 19:08 UTC, paul
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description paul 2021-06-06 19:08:01 UTC
Created attachment 225605 [details]
contents of net-mgmt/unbound-telemetry

I've tried to get net-mgmt/unbound_exporter to work, but without success.

I noticed that unbound_exporter hasn't been updated in years, but I did find another project, unbound-telemetry, that is much newer and it works.  So I created a port.  I am successfully running this port in my home lab.
Comment 1 Chris Hutchinson 2021-06-06 21:15:43 UTC
(In reply to paul from comment #0)
shar(1) (Shell ARchive) files are simply plain ASCII
text files. Can you please mark the attachment as
type: text/plain

:-)
Comment 2 paul 2021-06-06 23:53:42 UTC
Done!  I've set the shar attachment to be text/plain.

One detail that I just noticed is that I left a commented out MAINTAINER line in the Makefile.  I started the port with a copy of net-mgmt/nfs-exporter, so the commented out line points at asomers@FreeBSD.org.  This line should be deleted or the value changed to someone more appropriate.
Comment 3 Chris Hutchinson 2021-06-07 15:10:34 UTC
(In reply to paul from comment #2)
> I left a commented out MAINTAINER line in the Makefile.
> This line should be deleted or the value changed to
> someone more appropriate.
One would assume that because you were interested enough
to create hew port, that you would be interested enough
to be it's MAINTAINER. ;-)
IOW The MAINTAINER value in the Makefile should contain
_your_ chosen MAINTAINER email address. :-)
OTOH the MAINTAINER line should _never_ be blank/commented.
If all else fails, the value should be ports@FreeBSD.org

HTH
Comment 4 paul 2021-06-07 16:00:56 UTC
I would be happy to be the MAINTAINER.  My preferred email is paul@dokas.name

How should this detail get fixed?  Should I submit a new shar that includes this correction?
Comment 5 Chris Hutchinson 2021-06-07 16:18:38 UTC
(In reply to paul from comment #4)
Simply re-create the shar as you did before.
But change:
#MAINTAINER= line to:
MAINTAINER=	paul@dokas.name
You'll probably want to modify your registered
email address to include your actual name (note
the difference in the comments between yours and
mine here) -- paul@dokas.name vs. Chris Hutchinson.
As you're interested in becoming a MAINTAINER.
You'd do well to familiarize yourself with the
Porters Handbook:
https://docs.freebsd.org/en/books/porters-handbook/
You needen't memorize all of it. But _do_ attempt
to memorize the frequently used tasks. :-)

--Chris
Comment 6 Chris Hutchinson 2021-06-07 16:57:07 UTC
Points of interest to help accelerate your
port through the acceptance process:

 - Provide QA (Quality Assurnce)
provide proof that your port/changes actually work.
ports-mgmt/poudriere is the defacto choice for providing
the output to prove everything works as intended.
Other forms can include relevant output from build logs.
from within a jail(8), all of: make -DBATCH check-plist,
make stage-qa, make check-sanity, portlint. To name a few.
But as a rule, the output of ports-mgmt/poudriere is the
preferred proof.

 - Future maintence of your new port will require you to
become well familiar with git(1) if your not already
familiar. Even if you are. You'll still need to discover
how to use it with regards to maintaining ports, and
properly submitting patches.

 - Become informed.
You're also going to want to join at least the
freebsd-ports@ and the freebsd-ports-bugs@ mailing lists.
It may well be a good idea to also join the
dev-commits-ports-all@. As you're going to need to know if
things ever "go south" with any of the ports you maintain.

All of this is in the porters handbook that I mentioned
earlier. But these are some of the main points that will
help you "get up to speed".

--Chris