Page MenuHomeFreeBSD

New port: sysutils/intel-undervolt: Intel CPU undervolting tool
ClosedPublic

Authored by val_packett.cool on Jan 3 2019, 6:39 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jan 22, 5:09 AM
Unknown Object (File)
Tue, Jan 21, 10:47 PM
Unknown Object (File)
Oct 21 2024, 5:22 AM
Unknown Object (File)
Oct 1 2024, 9:18 PM
Unknown Object (File)
Sep 28 2024, 6:33 PM
Unknown Object (File)
Sep 10 2024, 1:36 AM
Unknown Object (File)
Sep 5 2024, 5:17 PM
Unknown Object (File)
Sep 5 2024, 11:29 AM

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

arrowd added inline comments.
sysutils/intel-undervolt/Makefile
5 ↗(On Diff #52516)

Aren't you reimplementing GH_TAGNAME with this?

0mp added inline comments.
sysutils/intel-undervolt/Makefile
5 ↗(On Diff #52516)

I think this is fine, see Example 5.14. Using USE_GITHUB to Access a Commit Between Two Versions in the Porter's Handbook.

23 ↗(On Diff #52516)

I think that we should use @sample here (see 8.6.9. @sample file [file] in the Porter's Handbook).

sysutils/intel-undervolt/Makefile
5 ↗(On Diff #52516)

Yeah, I always thought of DISTVERSIONSUFFIX=-gWHATEVER as a "higher level" wrapper around GH_TAGNAME

23 ↗(On Diff #52516)

Do the @ things work with PLIST_FILES (w/o dedicated pkg-plist file)?

sysutils/intel-undervolt/Makefile
23 ↗(On Diff #52516)

AFAIR, yes.

tobik added inline comments.
sysutils/intel-undervolt/Makefile
20 ↗(On Diff #52516)

Why +=?

23 ↗(On Diff #52516)

Yes, of course. PLIST_FILES is basically just appended to TMPPLIST. Just make sure to quote the entry like "@sample etc/intel-undervolt.conf.sample", so that make(1) treats it as a single word and it's added as one line to it.

linimon retitled this revision from New port: sysutils/intel-undervolt to New port: sysutils/intel-undervolt: Intel CPU undervolting tool.Jan 15 2019, 4:23 PM
This revision is now accepted and ready to land.Jan 20 2019, 1:38 PM
This revision was automatically updated to reflect the committed changes.

@greg_unrelenting.technology Committed. Thanks!

As a general rule, it's better if you also submit a bug on https://bugs.freebsd.org for new ports and updates, so that things can be tracked better. Bugzilla is also where more committers look for things to commit.