Re: MASTER_SITE_FEDORA_LINUX in bsd.sites.mk
Jason Helfman j...@freebsd.org wrote: I was looking at update bsd.sites.mk, and found that MASTER_SITE_FEDORA_LINUX is only used in one port. Any objection to moving this site-index into x11-themes/bluecurve-themes, and removing from bsd.sites.mk? There is also a referrence to it in bsd.linux-rpm.mk, but not certain how this should be handled. This seems to be a legacy site-index. This might better be asked on ports@ (Cc'd). I would think that Fedora is a sufficiently common distribution to warrant keeping this setting in a central location, in case of future need in a non-X port, unless its presence is causing problems. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Update of devel/glade3 and removal of devel/glade2
Hello, I'm writing the update of glade port. Gnome provides two version, 3.8.1 for GTK+-2.0 series and 3.10.2 for GTK+-3.0. Because the both version starts with 3.x.x as version number we should create a new port for the GTK+-3.0. Should I propose something like that ? devel/glade2 - removal (old, unused anymore) devel/glade3 - rename to devel/glade-gtk2 devel/glade-gtk3 - new port that I'll write for GTK+-3.0 soon Cheers, -- David Demelier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: xcb-util
I had fresh installed FreeBSD 9.0-RC3 ad than I updated to 9.0-Release. I ran portsnap fetch update and portmaster -a and xcb was updated. It happened day before when was /usr/ports/UPDATING update wtih portmaster -R -r xcb-util.0 which I ran yesterday and it happened what I wrote before. On Mon, Jan 16, 2012 at 5:17 PM, Freddie Cash fjwc...@gmail.com wrote: On Mon, Jan 16, 2012 at 3:11 PM, Chuck Swiger cswi...@mac.com wrote: On Jan 16, 2012, at 2:51 PM, ajtiM wrote: FreeBSD 9.0 is out, many people updated, new installation...KDE 4.7.4 is coming in the ports (I hope no) and now all this reinstallation for xcb-util. Is it not possible to synchronized a little with the other ports? You're the one managing your machine(s). If you want a package systems which releases less frequently than FreeBSD ports are updated, then either do not update your ports as rapidly, or consider switching to something like pkgsrc from NetBSD. Alternatively, switch to using pre-built, binary packages via the -P and -PP switches to portmaster/portupgrade, or even pkg_upgrade (from the sysutils/bsdadminscripts port). I need to reinstall about 300 ports (KDE, Firefox, libxul, GIMP...). It is to much... Why do you need to reinstall? Perhaps because he just completed an upgrade from 8.x to 9.0? While there are ways to mitigate the need for awhile (misc/compat8x, leaving old libraries around, various switches to portmaster/portupgrade to keep old versions of libs in /usr/local/compat, etc), eventually, one should reinstall all ports when upgrading between major versions of FreeBSD. However, one has the option of scheduling when that rebuilt/reinstall occurs. If you know a new version of X, KDE, Firefox are coming down the pipe soon, then why not wait until those major updates hit the ports tree? And then do everything all at once? Rather than reinstalling everything after the 8-9 upgrade, and then again for libxcb, then again for KDE, then again for Port X, Port Y, etc, etc, etc. Just because a new version hits the ports tree, doesn't mean you have to rush right out, this second, and upgrade to it. :) -- Freddie Cash fjwc...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Ports with version numbers going backwards: devel/py-repoze.who-testutil
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Tue Jan 17 2012 12:00:23 UTC. - *devel/py-repoze.who-testutil* po...@freebsd.org: py27-repoze.who-testutil-1.0.1 py27-repoze.who-testutil-1.0r1 | revision 1.2 | date: 2012/01/16 13:07:40; author: wen; state: Exp; lines: +3 -5 | - update to 1.0.1 | - reset maintainership to ports@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FW: p0f3 release candidate
On Fri, Jan 13, 2012 at 12:49:02AM -0500, Jason Hellenthal wrote: Ports maintainers and other ideals might be interested in the following. It purely needs more eyes at this point. If anyone has anything to update this port please let me know. If I don't get anything I'll just write the update myself soon(TM). -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Fwd: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses
tell me you want me to revert this patch, and do a portepoch. the solution would be for the submitter to work with the maintainer on a solution, or am I supposed to fix this without reversing this? Original Message Subject: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses Date: Tue, 17 Jan 2012 16:21:42 +0100 From: eha...@freebsd.org To: thomas.e.zan...@googlemail.com, eha...@freebsd.org, eha...@freebsd.org, scheid...@freebsd.org Synopsis: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses Responsible-Changed-From-To: ehaupt-scheidell Responsible-Changed-By: ehaupt Responsible-Changed-When: Tue Jan 17 16:21:42 CET 2012 Responsible-Changed-Why: Over to scheidel (last update to multimedia/mplayer). http://www.freebsd.org/cgi/query-pr.cgi?pr=164244 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Update of devel/glade3 and removal of devel/glade2
2012/1/17 David Demelier demelier.da...@gmail.com: devel/glade2 - removal (old, unused anymore) devel/glade3 - rename to devel/glade-gtk2 devel/glade-gtk3 - new port that I'll write for GTK+-3.0 soon BTW the filename of the executables are glade-2 for 2.x glade-3 for 3.8.x glade for 3.10.x and AFAIK, glade2 does code generation, and galde3 does not, though it's not recommended to use glade2 any more, I think it's still worth remaining for a while, as it's still working fine. Regards, Buganini ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Re: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses
On Tue, Jan 17, 2012 at 16:35, Michael Scheidell scheid...@freebsd.org wrote: tell me you want me to revert this patch, and do a portepoch. the solution would be for the submitter to work with the maintainer on a solution, or am I supposed to fix this without reversing this? Let's all calm down first :-) Please don't do portepoch, it's ugly. I'll see that I submit a fix soon. Riggs ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[solved] Re: mutt-devel with error
Hi list, add the variable in make: WITHOUT_GSSAPI # make install clean WITHOUT_GSSAPI=1 work fine now. * Luiz Gustavo (luizgust...@luizgustavo.pro.br) wrote: Hi list !!! I'm not able to do my mutt-devel work, I am with the following error below: [lgcosta@desktop] ~ mutt Undefined symbol gss_nt_service_name referenced from COPY relocation in /usr/local/bin/mutt[lgcosta@desktop] ~ [lgcosta@desktop] ~ [lgcosta@desktop] ~ uname -a FreeBSD desktop.luizgustavo.pro.br 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 can anyone help me with this? Compiled with these options: [root@desktop] /usr/ports/mail/mutt-devel# make showconfig === The following configuration options are available for mutt-devel-1.5.21_3: MUTT_ASPELL=on Enable aspell support MUTT_COMPRESSED_FOLDERS=on Enable compressed folders MUTT_CYRUS_SASL2=on Enable SASL2 authentication MUTT_DEBUG=off Enable debugging capabilities MUTT_FLOCK=off Enable flock() usage MUTT_GPGME=on Enable gpgme interface MUTT_GREETING_PATCH=on Enable greeting MUTT_HTML=on Enable HTML documentation MUTT_ICONV=on Enable iconv support MUTT_IDN=on Enable idn support MUTT_IFDEF_PATCH=off Enable ifdef feature MUTT_IMAP_HEADER_CACHE=on Enable imap header cache MUTT_ISPELL=off Enable ispell support MUTT_LOCALES_FIX=off Enable locales fix MUTT_MAILBOX_MANPAGES=on Install mbox.5/mmdf.5 manpages MUTT_MAILDIR_HEADER_CACHE=on Enable maildir header cache MUTT_MAILDIR_MTIME_PATCH=off Enable Maildir mtime patch MUTT_MBOX_HOOK_PATCH=off Enable enhanced mbox-hook MUTT_NCURSES=on Enable ncurses support MUTT_NCURSES_PORT=off Use ncurses from port MUTT_NNTP=off Enable news reader MUTT_PARENT_CHILD_MATCH_PATCH=off Enable parent/child match MUTT_QUOTE_PATCH=on Enable extended quoting MUTT_REVERSE_REPLY_PATCH=on Enable reverse_reply MUTT_SGMLFORMAT=on Enable sgml support MUTT_SIDEBAR_PATCH=on Enable sidebar MUTT_SIGNATURE_MENU=off Enable signature menu MUTT_SLANG=off Enable slang support MUTT_SMIME_OUTLOOK_COMPAT=on SMIME outlook compatible MUTT_SMTP=on Enable SMTP relay support MUTT_TRASH_PATCH=on Enable trash folder support MUTT_XML=on Use XML tools for docu === Use 'make config' to modify these settings -- Luiz Gustavo Costa (Powered by BSD) *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ mundoUnix - Consultoria em Software Livre http://www.mundounix.com.br ICQ: 2890831 / MSN: cont...@mundounix.com.br Tel: 55 (21) 4063-7110 / 8194-1905 / (11) 4063-0407 Blog: http://www.luizgustavo.pro.br ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
On 01/17/2012 03:56, Vitaly Magerya wrote: Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... Personally I think we should scrap the whole thing. It is an interesting idea, but the implementation has never fleshed out. It's also completely unclear what any of it means from an actual legal standpoint, and personally I'm not convinced that we aren't making things worse for the project by doing this. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote: On 01/17/2012 03:56, Vitaly Magerya wrote: Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... Personally I think we should scrap the whole thing. It is an interesting idea, but the implementation has never fleshed out. It's also completely unclear what any of it means from an actual legal standpoint, and personally I'm not convinced that we aren't making things worse for the project by doing this. How? I don't see the problem that makes things worse, I guess. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
On 17 Jan 2012 18:43, Chad Perrin c...@apotheon.net wrote: On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote: On 01/17/2012 03:56, Vitaly Magerya wrote: Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... Personally I think we should scrap the whole thing. It is an interesting idea, but the implementation has never fleshed out. It's also completely unclear what any of it means from an actual legal standpoint, and personally I'm not convinced that we aren't making things worse for the project by doing this. How? I don't see the problem that makes things worse, I guess. Well... the author and maintainer of the code isn't around any more. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Hi, after I did that: , | 20120116: | AFFECTS: users of x11/xcb-util | AUTHOR: ga...@freebsd.org | | x11/xcb-util was updated to 0.3.8 and was split in new modules. | Dependencies were adjusted but main port symbols were moved to a single | library, xcb-util.so. For this reason, all dependent ports must be | recompiled.If you use portmaster, run: | | # portmaster -R -r xcb-util-0 | | Or for portupgrade: | | # portupgrade -r xcb-util-0\* ` I got that: gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[3]: *** [xfwm4-workspace-settings] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. Any ideas? Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
On Tue, 17 Jan 2012, Chad Perrin wrote: On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote: On 01/17/2012 03:56, Vitaly Magerya wrote: Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... Personally I think we should scrap the whole thing. It is an interesting idea, but the implementation has never fleshed out. It's also completely unclear what any of it means from an actual legal standpoint, and personally I'm not convinced that we aren't making things worse for the project by doing this. How? I don't see the problem that makes things worse, I guess. In my not-a-lawyer view, I wonder if it puts some responsibility for accurately representing a license on FreeBSD and the ports system. We used this software because the FreeBSD ports system said the license was compatible for our use. Now it turns out otherwise, and we have millions in damages... There's the potential for someone to intentionally put the wrong license in a port to create such a situation. And to protect against that, will committers have to verify the license? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
Hello, On Tue, Jan 17, 2012 at 8:46 PM, Warren Block wbl...@wonkity.com wrote: On Tue, 17 Jan 2012, Chad Perrin wrote: On Tue, Jan 17, 2012 at 10:38:08AM -0800, Doug Barton wrote: On 01/17/2012 03:56, Vitaly Magerya wrote: Eitan Adler wrote: 1) Will licensing section ever appear in the Porters Handbook? :-) Yes Is someone actually working on it? If so, and is there some sort of target timeline? Back in 2010 when the framework was introduced, my general impression was that maintainers where advised to wait with the adoption until that chapter is written... Personally I think we should scrap the whole thing. It is an interesting idea, but the implementation has never fleshed out. It's also completely unclear what any of it means from an actual legal standpoint, and personally I'm not convinced that we aren't making things worse for the project by doing this. How? I don't see the problem that makes things worse, I guess. In my not-a-lawyer view, I wonder if it puts some responsibility for accurately representing a license on FreeBSD and the ports system. We used this software because the FreeBSD ports system said the license was compatible for our use. Now it turns out otherwise, and we have millions in damages... There's the potential for someone to intentionally put the wrong license in a port to create such a situation. And to protect against that, will committers have to verify the license? But surely this framework is for information purposes only? With standard disclaimers: if you really want to be sure, please check the official source, things might have changed since the port was last updated buyer (or porst user) beware Anything can go wrong, but it is (IMO) quite easy to state the intention of the FreeBSD Project in this case. But that requires that someone writes the chapter about this in the Porters Handbook... -- Regards, Torfinn Ingolfsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
mhonarc deprecated use of defined()
Mhonarc when run with perl 10.14.2 complains about its deprecated use of defined(%a_hash). I've replaced these defined() where used (not many) as shown in the attached patch files. Is there any interest in updating the mhonarc port to fix this issue? Rickie Kerndt Eugene, OR kern...@kerndt.com Makefile.diff Description: Binary data patch-lib__mhamain.pl Description: Binary data patch-lib__mhopt.pl Description: Binary data patch-lib__readmail.pl Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Adding licensing info to my ports: some questions
On 01/17/2012 14:35, Torfinn Ingolfsen wrote:
Anything can go wrong, but it is (IMO) quite easy to state the intention of
the FreeBSD Project in this case.
You're making the very common mistake of assuming that the law has
anything to do with reality. It doesn't. The fact that we're making
claims about legal issues opens the project up to a wide array of hairy
liability problems. It doesn't matter how baseless the lawsuit is,
sometimes just filing the suit creates enough damage to kill the thing
sued.
For example:
@${ECHO_MSG} === License ${_LICENSE} accepted by the user
*shudder*
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann rotkaps_spam_t...@gmx.dewrote: Hi, after I did that: , | 20120116: | AFFECTS: users of x11/xcb-util | AUTHOR: ga...@freebsd.org | | x11/xcb-util was updated to 0.3.8 and was split in new modules. | Dependencies were adjusted but main port symbols were moved to a single | library, xcb-util.so. For this reason, all dependent ports must be | recompiled.If you use portmaster, run: | | # portmaster -R -r xcb-util-0 | | Or for portupgrade: | | # portupgrade -r xcb-util-0\* ` I got that: gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[3]: *** [xfwm4-workspace-settings] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. Any ideas? Install sysutils/bsdadminscripts and use pkg_libchk to find the missed dependency. I just tracked down that metacity had been missed causing several ports to fail, but your case may well be something different. -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Upgrading libs with many dependent ports
I have just been cleaning up the mess caused by the upgrade of xcb-utils. On my systmes I have hundreds of ports that will be re-built by the methods listed in UPDATING, even though the vast majority of them are only dependent on other ports that are dependent on xcb-utils, but don't actually load any of the libraries in xcb-utils. It is a huge waste of time and CPU cycles. I think that I can see two ways of eliminating the rebuilding of ports that don't need it. One is rather manual but can be done now while the other wou;d be automatic, but would need to be written by someone who is far better at writing shell scripts than I. The manual method would be to install sysutils/bsdadminscripts and use a command like `pkg_libchk | grep -E xcb-.+.so | sort tmpfile` to provide a list of ports that actually are linked to the libraries in question. This would be fed into portmaster to rebuild just these ports. (I guess I could use awk and uniq to remove repeats.) Should this become a preferred method of handling this problem? -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrading libs with many dependent ports
On Tue, Jan 17, 2012 at 05:51:11PM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
The manual method would be to install sysutils/bsdadminscripts and
use a command like `pkg_libchk | grep -E xcb-.+.so | sort
tmpfile` to provide a list of ports that actually are linked to the
libraries in question.
FWIW, I some years ago wrote up a quickdirty perl script to find
missing or out of date libs. It pulls out and warns about missing
libs, stuff in compat/pkg (held over after upgrade by
portupgrade/portmaster), and stuff in the base /usr/lib/compat (handy
when crossing major versions, and potentially other big upheavals).
It's only about a k; I'll attach it.
I pretty much wind up ldd'ing /usr/local/{bin/*,sbin/*,lib/*.so*} and
running the results through the script. Usually something like `cd
/usr/local/bin ; ldd * /tmp/ldd.bin ; lddchk.pl /tmp/ldd.bin`.
That tells me the files; then I can use my brain or pkg_which to tell
me which packages are involved. I'm happy with that level of
automation, because I like keeping my brain firmly in the loop on such
things, but it wouldn't be too hard to extend it to do its own walks
over the filesystem, etc.
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrading libs with many dependent ports
On Tue, Jan 17, 2012 at 6:09 PM, Matthew D. Fuller fulle...@over-yonder.net
wrote:
On Tue, Jan 17, 2012 at 05:51:11PM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
The manual method would be to install sysutils/bsdadminscripts and
use a command like `pkg_libchk | grep -E xcb-.+.so | sort
tmpfile` to provide a list of ports that actually are linked to the
libraries in question.
FWIW, I some years ago wrote up a quickdirty perl script to find
missing or out of date libs. It pulls out and warns about missing
libs, stuff in compat/pkg (held over after upgrade by
portupgrade/portmaster), and stuff in the base /usr/lib/compat (handy
when crossing major versions, and potentially other big upheavals).
It's only about a k; I'll attach it.
I pretty much wind up ldd'ing /usr/local/{bin/*,sbin/*,lib/*.so*} and
running the results through the script. Usually something like `cd
/usr/local/bin ; ldd * /tmp/ldd.bin ; lddchk.pl /tmp/ldd.bin`.
That tells me the files; then I can use my brain or pkg_which to tell
me which packages are involved. I'm happy with that level of
automation, because I like keeping my brain firmly in the loop on such
things, but it wouldn't be too hard to extend it to do its own walks
over the filesystem, etc.
Take a look at pkg_chklib. It is quite optimized and runs multiple checks
in parallel so that
you can run it on 1100 ports in about 1.5 minutes. Here is a sample o this
output:
%pkg_libchk | grep -E xcb-.+.so | sort
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-event.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-event.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-atom.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-aux.so.0
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-event.so.1
vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so
misses libxcb-keysyms.so.1
vlc-1.1.13,3:
/usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses
libxcb-keysyms.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-atom.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-aux.so.0
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-event.so.1
%
And it is already in ports.
--
R. Kevin Oberman, Network Engineer
E-mail: kob6...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Kevin Oberman kob6...@gmail.com wrote: On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann rotkaps_spam_t...@gmx.dewrote: gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[3]: *** [xfwm4-workspace-settings] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. Any ideas? Install sysutils/bsdadminscripts and use pkg_libchk to find the missed dependency. I just tracked down that metacity had been missed causing several ports to fail, but your case may well be something different. Ooops: # pkg_libchk Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-atom.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so misses libxcb-keysyms.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses libxcb-keysyms.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libclock.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libclock.so
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
On Tue, Jan 17, 2012 at 10:32 PM, Heino Tiedemann rotkaps_spam_t...@gmx.dewrote: Kevin Oberman kob6...@gmail.com wrote: On Tue, Jan 17, 2012 at 11:18 AM, Heino Tiedemann rotkaps_spam_t...@gmx.dewrote: gmake[3]: Entering directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' CC xfwm4_settings-xfwm4-settings.o CCLD xfwm4-settings CC xfwm4_tweaks_settings-tweaks-settings.o CCLD xfwm4-tweaks-settings CC xfwm4_workspace_settings-workspace-settings.o CCLD xfwm4-workspace-settings libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or unhandled argument `/usr/local/lib/libxcb-aux.la' gmake[3]: *** [xfwm4-workspace-settings] Error 1 gmake[3]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3/settings-dialogs' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-wm/xfce4-wm/work/xfwm4-4.8.3' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. *** Error code 1 Stop in /usr/ports/x11-wm/xfce4-wm. Any ideas? Install sysutils/bsdadminscripts and use pkg_libchk to find the missed dependency. I just tracked down that metacity had been missed causing several ports to fail, but your case may well be something different. Ooops: # pkg_libchk Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/thunarx-2/thunar-uca.so misses libxcb-atom.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-aux.so.0 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-event.so.1 Thunar-1.3.0: /usr/local/lib/xfce4/panel/plugins/libthunar-tpa.so misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnck-urgency-monitor misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/bin/wnckprop misses libxcb-atom.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-aux.so.0 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-event.so.1 libwnck-2.30.6: /usr/local/lib/libwnck-1.so.22 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libxfcegui4.so.7 misses libxcb-atom.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-aux.so.0 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-event.so.1 libxfce4gui-4.8.1: /usr/local/lib/libglade/2.0/libxfce4.so misses libxcb-atom.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-aux.so.0 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-event.so.1 mousepad-0.2.16_8: /usr/local/bin/mousepad misses libxcb-atom.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-aux.so.0 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-event.so.1 squeeze-0.2.3_2: /usr/local/bin/squeeze misses libxcb-atom.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-aux.so.0 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-event.so.1 thunar-vfs-1.2.0_1: /usr/local/lib/libthunar-vfs-1.so.5 misses libxcb-atom.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so misses libxcb-keysyms.so.1 vlc-1.1.13,3: /usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses libxcb-keysyms.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop misses libxcb-atom.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-aux.so.0 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-event.so.1 xfce4-desktop-4.8.3: /usr/local/bin/xfdesktop-settings misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libactions.so misses libxcb-atom.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-aux.so.0 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so misses libxcb-event.so.1 xfce4-panel-4.8.6: /usr/local/lib/xfce4/panel/plugins/libapplicationsmenu.so
Re: cannot build x11-wm/xfce4-wm after upgrade x11/xcb-util
Michael Johnson a...@ahze.net wrote: Out of curiosity, what does 'grep xcb-aux /usr/local/libdata/pkgconfig/*' show? Nothing. No Output. Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrading libs with many dependent ports
On 01/17/2012 07:51 PM, Kevin Oberman wrote:
I have just been cleaning up the mess caused by the upgrade of xcb-utils.
On my systmes I have hundreds of ports that will be re-built by the methods
listed in UPDATING, even though the vast majority of them are only
dependent on other ports that are dependent on xcb-utils, but don't
actually load any of the libraries in xcb-utils. It is a huge waste of time
and CPU cycles.
I think that I can see two ways of eliminating the rebuilding of ports that
don't need it. One is rather manual but can be done now while the other
wou;d be automatic, but would need to be written by someone who is far
better at writing shell scripts than I.
The manual method would be to install sysutils/bsdadminscripts and use a
command like `pkg_libchk | grep -E xcb-.+.so | sort tmpfile` to provide
a list of ports that actually are linked to the libraries in question. This
would be fed into portmaster to rebuild just these ports. (I guess I could
use awk and uniq to remove repeats.)
Should this become a preferred method of handling this problem?
You mean something like the attached script?
Type
perl pkg_libchk xcb-util-0.3.6,1
and it tells you all the ports that have xcb-util-0.3.6,1 as a lib-depends.
On my system I get 38 ports that require upgrading. All the other 248
dependencies installed on my system are only run-depends, and so don't
need to be upgraded.
I wrote it using perl, because I think a shell script would be quite a
bit slower. And it is already quite slow as it is.
It looks worth implementing, because it looks like it could save
considerable compilation time. If other people think this tool is
useful, someone could clean up the script (e.g. it isn't PREFIX
friendly, and assumes the port database is /var/db/pkg, etc). It could
also be written as a C program without too much trouble.
#!/usr/bin/perl -w
use strict;
my %lib_found;
my %ldd;
sub pkg_libchk {
my $req=/var/db/pkg/$_[0]/+REQUIRED_BY;
return if ! -e $req;
my @libs;
open(my $C,/var/db/pkg/$_[0]/+CONTENTS) || die;
while ($C) {
if (!/^\@/ /\/(lib[^\/]+\.so)$/) {
push @libs,$1;
}
}
close $C;
return if $#libs==-1;
open(my $R,$req) || die;
while (my $r=$R) {
next if defined($lib_found{$r});
chomp $r;
open(my $C,/var/db/pkg/$r/+CONTENTS) || die;
while (my $f=$C) {
chomp $f;
if ($f !~ /^@/) {
if (!defined($ldd{$f})) {
$ldd{$f} = `ldd /usr/local/$f 2/dev/null`;
}
foreach my $l (@libs) {
if ($ldd{$f} =~/$l/) {
if (!defined($lib_found{$r})) {
print $r\n;
$lib_found{$r}=1;
pkg_libchk($r);
goto DONE;
}
}
}
}
}
DONE:
close($C);
}
close($R);
}
die if ! -e /var/db/pkg/$ARGV[0];
pkg_libchk($ARGV[0]);
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Upgrading libs with many dependent ports
On 01/17/2012 08:43 PM, Kevin Oberman wrote:
On Tue, Jan 17, 2012 at 6:09 PM, Matthew D. Fullerfulle...@over-yonder.net
wrote:
On Tue, Jan 17, 2012 at 05:51:11PM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
The manual method would be to install sysutils/bsdadminscripts and
use a command like `pkg_libchk | grep -E xcb-.+.so | sort
tmpfile` to provide a list of ports that actually are linked to the
libraries in question.
FWIW, I some years ago wrote up a quickdirty perl script to find
missing or out of date libs. It pulls out and warns about missing
libs, stuff in compat/pkg (held over after upgrade by
portupgrade/portmaster), and stuff in the base /usr/lib/compat (handy
when crossing major versions, and potentially other big upheavals).
It's only about a k; I'll attach it.
I pretty much wind up ldd'ing /usr/local/{bin/*,sbin/*,lib/*.so*} and
running the results through the script. Usually something like `cd
/usr/local/bin ; ldd * /tmp/ldd.bin ; lddchk.pl /tmp/ldd.bin`.
That tells me the files; then I can use my brain or pkg_which to tell
me which packages are involved. I'm happy with that level of
automation, because I like keeping my brain firmly in the loop on such
things, but it wouldn't be too hard to extend it to do its own walks
over the filesystem, etc.
Take a look at pkg_chklib. It is quite optimized and runs multiple checks
in parallel so that
you can run it on 1100 ports in about 1.5 minutes. Here is a sample o this
output:
%pkg_libchk | grep -E xcb-.+.so | sort
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/create-branching-keyboard misses
libxcb-event.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-atom.so.1
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-aux.so.0
gok-2.30.1,1: /usr/local/bin/gok misses libxcb-event.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-atom.so.1
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-aux.so.0
nautilus-open-terminal-0.18_4:
/usr/local/lib/nautilus/extensions-2.0/libnautilus-open-terminal.so misses
libxcb-event.so.1
vlc-1.1.13,3: /usr/local/lib/vlc/plugins/control/libglobalhotkeys_plugin.so
misses libxcb-keysyms.so.1
vlc-1.1.13,3:
/usr/local/lib/vlc/plugins/video_output/libxcb_window_plugin.so misses
libxcb-keysyms.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-atom.so.1
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-aux.so.0
yelp-2.30.2_1: /usr/local/bin/yelp misses libxcb-event.so.1
%
And it is already in ports.
And in my other email, I might have reinvented the wheel!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
