pkg-plist in poudriere

[Helmut]

Hello,

[feature request] Generate pkg-plist or pkg-plist diff during testport. · Issue #659 · freebsd/poudriere

Poudriere can tell me what changes I need to make to my pkg-plist file, but the output is not in any machine-readable form. I'd estimate that around 20-30% of the time that I spend on updating a po...

github.com

Poudriere can tell me what changes I need to make to my pkg-plist file

Where does it tell me, at what point?

Thank you!

 

[SirDice]

I generally build a port first, outside of poudriere and use make makeplist > pkg-plist. Then go through the result (or compare it with the previous version) and make any necessary adjustments. Once I'm somewhat satisfied the port is correct I give a run through poudriere-testport(8) to verify things are correct.

The feature looks interesting though, I presume the details will be in the build logs. For poudriere I can highly recommend setting up the web interface for it, that makes it so much easier to see what's going on and check specific build logs. You can find example configurations for Apache, nginx and Caddy in /usr/local/share/examples/poudriere/.

 

[Helmut]

I generally build a port first, outside of poudriere and use make makeplist > pkg-plist. Then go through the result (or compare it with the previous version) and make any necessary adjustments. Once I'm somewhat satisfied the port is correct I give a run through poudriere-testport(8) to verify things are correct.

The feature looks interesting though, I presume the details will be in the build logs. For poudriere I can highly recommend setting up the web interface for it, that makes it so much easier to see what's going on and check specific build logs. You can find example configurations for Apache, nginx and Caddy in /usr/local/share/examples/poudriere/.

I do have set up poudriere including the web interface but I never found where it would point to the pkg-plist. I hoped I could do everything with testport. I don't want to make anything outside poudriere, if, I wouldn't require poudriere at all.

 

[Mirror176]

The build log should list any discrepancies between the pkg-plist and what it detects was installed. Look near the end of the log where it does staging/qa stuff. I thought it was possible to use makeplist inside a poudriere testport operation but you need to write or copy it to a place outside that jail. Some ports also have bypassed using plist which I suspected was a workaround to maintaining such a list.