Date: Wed, 05 Apr 2006 10:35:09 +1000 From: freebsd-questions@auscert.org.au To: freebsd-questions@freebsd.org Subject: How to handle 'local' ports/packages? Message-ID: <200604050035.k350Z9cP098258@app.auscert.org.au>
next in thread | raw e-mail | index | archive | help
Hi, Can anyone give me a tip on how to properly integrate a local package so that I don't get: pkg_delete: package xxxxx has no origin recorded errors? I've tried adding a line like: @comment ORIGIN:local/xxxx to the +CONTENTS file for the package, but then portmanager complains that it is nonexistent and won't complete 'portmanager -s'. To make matters more awkward, this package is built from a closed-source binary distribution and thus can't be properly ported, so I can't set it up properly. What I'd like is for management tools to acknowledge its existence, yet ignore it entirely for the purposes of maintenance. For instance, I have already made it a held package under pkgtools.conf, which seems to satisfy portupgrade ok. I'm happy with the package I've made, as it enables me to check what version is installed with pkg_info, I just want it to play nicely with other real ports! joel -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604050035.k350Z9cP098258>