Re: Creating port from pre-built package
Am 11.02.21 um 18:12 schrieb Shawn Webb: On Thu, Feb 11, 2021 at 06:09:52PM +0100, Patrick M. Hausen wrote: Hi all, Am 11.02.2021 um 18:03 schrieb Chris : On 2021-02-11 08:26, Shawn Webb wrote: Hey all, The Splunk universal forwarder for FreeBSD is distributed as a package tarball that you can use `pkg add` on. I'm in a position where I'd like to create a port of the package so that I can automate certain tasks. Reverse engineer a package? I think that will violate the NDA you signed. ;-) Really. Unless the package is simply a wrapper of a binary blob. You'll need to *build* the port, as part of the package creation process. That is, unless I've *completely* misunderstood your intent here. :-) The binary package is provided by the software manufacturer without source code. Still one might want to have a port available so one can put the port in poudriere and have it available in one's own package repo. Right, I'm not aiming to recompile the software. I'm looking to simply create a new package.txz with the pre-built artifacts included. Adding to the previous mail on how a FreeBSD port might be used to install this binary package: Be sure to be allowed to re-package the binary distribution that you want to use in this port. The license may explicitly forbid the distribution of derived works of any kind. Do also set the LICENSE and specifically the LICENSE_PERMS variable in the port's Makefile to indicate whether the FreeBSD package that will be built from this port may be created, distributed, possibly also sold. Regards, STefan OpenPGP_signature Description: OpenPGP digital signature
Re: Creating port from pre-built package
Am 11.02.21 um 18:12 schrieb Shawn Webb:
On Thu, Feb 11, 2021 at 06:09:52PM +0100, Patrick M. Hausen wrote:
Hi all,
Am 11.02.2021 um 18:03 schrieb Chris :
On 2021-02-11 08:26, Shawn Webb wrote:
Hey all,
The Splunk universal forwarder for FreeBSD is distributed as a package
tarball that you can use `pkg add` on. I'm in a position where I'd
like to create a port of the package so that I can automate certain
tasks.
Reverse engineer a package? I think that will violate the NDA you
signed. ;-)
Really. Unless the package is simply a wrapper of a binary blob. You'll
need to *build* the port, as part of the package creation process.
That is, unless I've *completely* misunderstood your intent here. :-)
The binary package is provided by the software manufacturer without
source code.
Still one might want to have a port available so one can put the port
in poudriere and have it available in one's own package repo.
Right, I'm not aiming to recompile the software. I'm looking to simply
create a new package.txz with the pre-built artifacts included.
I shouldn't be too hard to create a port, just be careful to consider
the architecture dependency of the binary package you are using.
If multiple architectures and OS releases are supported, then you'll
have to create the package name from those parameters and provide
distinfo data for all supported combinations of architecture and
OS release. You can override the name of the DISTINFO_FILE in the
port's Makefile to have separate distinfo files per arch/version.
In the port's Makefile extract the contents of the correct package
into the stage directory, have dummy targets for phases that are not
reuquired (e.g. an empty do-stage to have the stage done marker set
in the ${WRKSRC} directory) and provide a pkg-plist (possibly multiple
variants selected by the PLIST variable, if there are arch/version
specific differences).
Use ONLY_FOR_ARCH and IGNORE to limit the package building to those
architectures and releases that are supported, to prevent package
fall-out messages and to give ports users a reasonable error message
when trying to build the port on an unsupported system.
The generated package will have the meta-data from your port. If
you want to preserve some meta-date from the pre-built package, then
extract it from the extracted distfile, e.g. in the build phase.
Else use NO_BUILD to suppress this and possibly other phases that
are not required (empty dummy targets will do as well).
Regards, STefan
OpenPGP_signature
Description: OpenPGP digital signature
Re: MFH commit issues [UPDATE: (hopefully) RESOLVED]
I realized this port doesn't exist in 2021Q1 since it's so new, and that's why I couldn't MFH. I reverted this in r564997. Sorry for the confusion, and sorry again if I committed in the wrong place, and sorry yet again if I sent too many emails. -Neel On 2021-02-11 21:26, Neel Chauhan wrote: Also, I am not able to MFH this port for some reason. Please help. Also, could someone with access to 2021Q1 revert r564996 and MFH r564995 on my behalf? Sorry if I made a big mistake here. I was trying to commit the MFH but couldn't. -Neel On 2021-02-11 21:19, Neel Chauhan wrote: Hi freebsd-ports@, I made a MFH commit for www/oauth2-proxy which was a security update. However, when I did it, it initially didn't MFH. To "commit" it, I had to run "svn propdel svn:mergeinfo www". After this, it didn't really do the MFH but instead says "props deleted". Sorry for the issues caused by this. The "MFH": https://svnweb.freebsd.org/ports?view=revision=564996 Could some of you please fix the issues with the branch? -Neel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: MFH commit issues
Also, I am not able to MFH this port for some reason. Please help. Also, could someone with access to 2021Q1 revert r564996 and MFH r564995 on my behalf? Sorry if I made a big mistake here. I was trying to commit the MFH but couldn't. -Neel On 2021-02-11 21:19, Neel Chauhan wrote: Hi freebsd-ports@, I made a MFH commit for www/oauth2-proxy which was a security update. However, when I did it, it initially didn't MFH. To "commit" it, I had to run "svn propdel svn:mergeinfo www". After this, it didn't really do the MFH but instead says "props deleted". Sorry for the issues caused by this. The "MFH": https://svnweb.freebsd.org/ports?view=revision=564996 Could some of you please fix the issues with the branch? -Neel signature.asc Description: OpenPGP digital signature
MFH commit issues
Hi freebsd-ports@, I made a MFH commit for www/oauth2-proxy which was a security update. However, when I did it, it initially didn't MFH. To "commit" it, I had to run "svn propdel svn:mergeinfo www". After this, it didn't really do the MFH but instead says "props deleted". Sorry for the issues caused by this. The "MFH": https://svnweb.freebsd.org/ports?view=revision=564996 Could some of you please fix the issues with the branch? -Neel signature.asc Description: OpenPGP digital signature
Re: Creating port from pre-built package
On 2021-02-11 09:08, Shawn Webb wrote: On Thu, Feb 11, 2021 at 09:03:19AM -0800, Chris wrote: On 2021-02-11 08:26, Shawn Webb wrote: > Hey all, > > The Splunk universal forwarder for FreeBSD is distributed as a package > tarball that you can use `pkg add` on. I'm in a position where I'd > like to create a port of the package so that I can automate certain > tasks. Reverse engineer a package? I think that will violate the NDA you signed. ;-) Really. Unless the package is simply a wrapper of a binary blob. You'll need to *build* the port, as part of the package creation process. That is, unless I've *completely* misunderstood your intent here. :-) It's literally a package of pre-built binaries. You can install it by running: # pkg add ./splunkforwarder-8.0.7-cbe73339abca-freebsd-11.1-amd64.txz Here's what `pkg info` shows: $ pkg info -F splunkforwarder-8.0.7-cbe73339abca-freebsd-11.1-amd64.txz [11:55:13] splunkforwarder-8.0.7 Name : splunkforwarder Version: 8.0.7 Origin : sysutils/splunk Architecture : FreeBSD:11:amd64 Prefix : /opt Categories : Licenses : Maintainer : eng-rele...@splunk.com WWW: http://www.splunk.com Comment: Splunk> The platform for machine data. Annotations: no_provide_shlib: yes FreeBSD_version: 1101001 Flat size : 56.6MiB Description: Splunk> The platform for machine data. (C) 2005-2020 Splunk Inc. All rights Reserved I'm not looking to re-build the binaries, but rather just use ports to recreate the package given a pre-existing package tarball. Well it's missing Categories && Licenses, and the Prefix is wrong. So changes are in order. Aside from unpacking it somewhere, and cobbling up a script to re-pack(age) it. I'm at a loss. But it *does* seem like it might be possible. Good luck. Thanks, --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Creating port from pre-built package
On Thu, Feb 11, 2021 at 06:09:52PM +0100, Patrick M. Hausen wrote: > Hi all, > > > Am 11.02.2021 um 18:03 schrieb Chris : > > > > On 2021-02-11 08:26, Shawn Webb wrote: > >> Hey all, > >> The Splunk universal forwarder for FreeBSD is distributed as a package > >> tarball that you can use `pkg add` on. I'm in a position where I'd > >> like to create a port of the package so that I can automate certain > >> tasks. > > Reverse engineer a package? I think that will violate the NDA you > > signed. ;-) > > > > Really. Unless the package is simply a wrapper of a binary blob. You'll > > need to *build* the port, as part of the package creation process. > > That is, unless I've *completely* misunderstood your intent here. :-) > > The binary package is provided by the software manufacturer without > source code. > > Still one might want to have a port available so one can put the port > in poudriere and have it available in one's own package repo. > Right, I'm not aiming to recompile the software. I'm looking to simply create a new package.txz with the pre-built artifacts included. Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 https://git-01.md.hardenedbsd.org/HardenedBSD/pubkeys/src/branch/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: Creating port from pre-built package
Hi all, > Am 11.02.2021 um 18:03 schrieb Chris : > > On 2021-02-11 08:26, Shawn Webb wrote: >> Hey all, >> The Splunk universal forwarder for FreeBSD is distributed as a package >> tarball that you can use `pkg add` on. I'm in a position where I'd >> like to create a port of the package so that I can automate certain >> tasks. > Reverse engineer a package? I think that will violate the NDA you > signed. ;-) > > Really. Unless the package is simply a wrapper of a binary blob. You'll > need to *build* the port, as part of the package creation process. > That is, unless I've *completely* misunderstood your intent here. :-) The binary package is provided by the software manufacturer without source code. Still one might want to have a port available so one can put the port in poudriere and have it available in one's own package repo. We have ports for proprietary RAID management blobs, we used to have a port for flash, etc. etc. HTH, Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein signature.asc Description: Message signed with OpenPGP
Re: Creating port from pre-built package
On Thu, Feb 11, 2021 at 09:03:19AM -0800, Chris wrote: > On 2021-02-11 08:26, Shawn Webb wrote: > > Hey all, > > > > The Splunk universal forwarder for FreeBSD is distributed as a package > > tarball that you can use `pkg add` on. I'm in a position where I'd > > like to create a port of the package so that I can automate certain > > tasks. > Reverse engineer a package? I think that will violate the NDA you > signed. ;-) > > Really. Unless the package is simply a wrapper of a binary blob. You'll > need to *build* the port, as part of the package creation process. > That is, unless I've *completely* misunderstood your intent here. :-) It's literally a package of pre-built binaries. You can install it by running: # pkg add ./splunkforwarder-8.0.7-cbe73339abca-freebsd-11.1-amd64.txz Here's what `pkg info` shows: $ pkg info -F splunkforwarder-8.0.7-cbe73339abca-freebsd-11.1-amd64.txz [11:55:13] splunkforwarder-8.0.7 Name : splunkforwarder Version: 8.0.7 Origin : sysutils/splunk Architecture : FreeBSD:11:amd64 Prefix : /opt Categories : Licenses : Maintainer : eng-rele...@splunk.com WWW: http://www.splunk.com Comment: Splunk> The platform for machine data. Annotations: no_provide_shlib: yes FreeBSD_version: 1101001 Flat size : 56.6MiB Description: Splunk> The platform for machine data. (C) 2005-2020 Splunk Inc. All rights Reserved I'm not looking to re-build the binaries, but rather just use ports to recreate the package given a pre-existing package tarball. Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 https://git-01.md.hardenedbsd.org/HardenedBSD/pubkeys/src/branch/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: Creating port from pre-built package
On 2021-02-11 08:26, Shawn Webb wrote: Hey all, The Splunk universal forwarder for FreeBSD is distributed as a package tarball that you can use `pkg add` on. I'm in a position where I'd like to create a port of the package so that I can automate certain tasks. Reverse engineer a package? I think that will violate the NDA you signed. ;-) Really. Unless the package is simply a wrapper of a binary blob. You'll need to *build* the port, as part of the package creation process. That is, unless I've *completely* misunderstood your intent here. :-) Being a ports newb, I'm not sure how to properly create a port from a pre-built package. Does anyone have any non-xkcd pointers[1]? [1]: https://xkcd.com/138/ Thanks, --Chris ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Creating port from pre-built package
Hey all, The Splunk universal forwarder for FreeBSD is distributed as a package tarball that you can use `pkg add` on. I'm in a position where I'd like to create a port of the package so that I can automate certain tasks. Being a ports newb, I'm not sure how to properly create a port from a pre-built package. Does anyone have any non-xkcd pointers[1]? [1]: https://xkcd.com/138/ Thanks, -- Shawn Webb Cofounder / Security Engineer HardenedBSD GPG Key ID: 0xFF2E67A277F8E1FA GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9 3633 C85B 0AF8 AB23 0FB2 https://git-01.md.hardenedbsd.org/HardenedBSD/pubkeys/src/branch/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc signature.asc Description: PGP signature
Re: Building a port with poudriere that depends on a cargo crate that needs net access
On Wednesday, February 10, 2021 2:37:14 PM EST Matthew D. Fuller wrote: > In this case, x-ref > https://github.com/addr-rs/addr/issues/6 > so apparently there's some way to point it at a manually pre-fetched > list. Thanks that did the trick, I was able to pull down a copy of a list and have it being patched in so it is available during the build stage. signature.asc Description: This is a digitally signed message part.
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ multimedia/kodi-addon-inputstream.adaptive-devel | 2.6.0 | 2.6.7-matrix +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
