Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Wed, 26 Aug 2009, Doug Barton wrote: Jonathan wrote: On 8/24/2009 8:23 PM, Andrew Reilly wrote: Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? I've found pkg_tree to be useful for that. http://www.freebsd.org/cgi/url.cgi?ports/ports-mgmt/pkg_tree/pkg-descr The feature I use the most is pkg_tree -tq which gives a list of all ports that are not depended on by any other ports, i.e. the minimal set to manually reinstall to replicate a set of installed ports on another machine. portmaster -l will give you a list of ports in the following categories: === Root ports (No dependencies, not depended on) === Trunk ports (No dependencies, are depended on) === Branch ports (Have dependencies, are depended on) === Leaf ports (Have dependencies, not depended on) There is a procedure in the man page that describes how to use that information to do a clean reinstall of your ports. Is there any way to graph that visually? -Warren Block * Rapid City, South Dakota USA ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Andrew Reilly wrote: On Mon, Aug 24, 2009 at 06:18:47PM -0700, Kevin Oberman wrote: If you have portupgrade, I would suggest 'portupgrade -rfx firefox firefox'. portupgrade works by building a dependency graph of the needed ports and builds te tree from the root. This should get rid of all but a handful of ports. I've stopped using portupgrade in favour of portmaster, Always nice to hear from a happy customer. :) but I don't see a ready equivalent to this with portmaster, hence my dumb script. In particular, I don't think that portmaster can combine the -r and -x flags (depend and exclude), Ummm, why not? It's a little hard to represent in the man page because there are so many flags, but -x is included in the common flags list at the top, and the man page does indicate that -r will take the common flags. You'd have to write it: portmaster -x firefox -r firefox-2.34 (substitute the actual value for the installed firefox port) but it should work. There are at least three other ways to do something similar. One would be to use -i instead of -x, another would be an +IGNOREME file. Read the man page for how to use the latter. Yet another way to do what you proposed in the part of your post that I snipped (building based on a list) would have been to do this: pkg_info -q -R firefox-2* list portmaster `cat list` That's probably the simplest way to do what you were trying to accomplish, and would have had the benefit of portmaster caching all the data on up to date dependencies, and building the things in the list in proper dependency order. Sorry to jump in after the fact with this news, but hopefully it will help someone else. and when I've done -f -r in combination before, then it seems to build the entire transitive closure of dependencies, rather than just the immediate ones. The -f option means rebuild everything in the chain, no matter what. If you just want to rebuild everything that has a dependency on the port you specify with -r, that is the default, you don't need -f. hth, Doug -- This .signature sanitized for your protection ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Andrew Reilly wrote: I've stopped using portupgrade in favour of portmaster, but I don't see a ready equivalent to this with portmaster, hence my dumb script. In particular, I don't think that portmaster can combine the -r and -x flags (depend and exclude), and when I've done -f -r in combination before, then it seems to build the entire transitive closure of dependencies, rather than just the immediate ones. Hence my question about a tool to manipulate the dependency graph as a graph... You can always play with http://www.lpthe.jussieu.fr/~talon/pkgupgrade which, i think, is a lot easier to hack than portupgrade, and includes, like portupgrade, a dependency graph computation. Beware that there is not a unique way to compute the upgrade order, so you cannot be sure to get an optimal way. In a few words, the problem is to get a total order on a set of ports compatible with a partial order given by dependency. There is always such a total order, but it is not unique. -- Michel TALON ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Hi Doug, On Mon, Aug 24, 2009 at 11:31:42PM -0700, Doug Barton wrote: portmaster -x firefox -r firefox-2.34 (substitute the actual value for the installed firefox port) but it should work. There are at least three other ways to do something similar. One would be to use -i instead of -x, another would be an +IGNOREME file. Read the man page for how to use the latter. Yet another way to do what you proposed in the part of your post that I snipped (building based on a list) would have been to do this: pkg_info -q -R firefox-2* list portmaster `cat list` That's probably the simplest way to do what you were trying to accomplish, and would have had the benefit of portmaster caching all the data on up to date dependencies, and building the things in the list in proper dependency order. Sorry to jump in after the fact with this news, but hopefully it will help someone else. The -f option means rebuild everything in the chain, no matter what. If you just want to rebuild everything that has a dependency on the port you specify with -r, that is the default, you don't need -f. Thanks for the tutorial! I need to polish my portmaster foo. I'm sure that I tried the -r -x combination and faild, but perhaps there was another reason. Even so, it should have been obvous to me that just running portmaster on the list of firefox dependents would do the right thing. Must have been having a dumb day. Cheers, -- Andrew ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Andrew Reilly wrote: On Sun, Aug 23, 2009 at 10:26:25PM -0400, Joe Marcus Clarke wrote: You can set WITH_GECKO=libxul in make.conf, and most of these should go away. I've done that (and installed libxul!) and re-built all of the ports in firefox-2.*/+REQUIRED_BY, and my list is now: alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 gnome-control-center-2.26.0_2 gimp-2.6.6,2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome2-2.26.3 gtkam-gnome-0.1.16.1_1 hamster-applet-2.26.3_1 orca-2.26.3_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 That's a lot shorter than it was before, but still clearly quite long. In most of these I can't see where the firefox dependency is coming from. For instance, the gimp meta-port is still here, but gimp-app has moved over to the libxul-1.9 +REQUIRED_BY list. Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? You can install pkg_tree (written in perl). It will list dependencies in hierarchical tree. example for GD # pkg_tree -v gd-2 gd-2.0.35_1,1 |\__ png-1.2.38 |\__ jpeg-7 |\__ pkg-config-0.23_1 |\__ freetype2-2.3.9_1 | \__ pkg-config-0.23_1 \__ libiconv-1.13.1 Miroslav Lachman ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Doug Barton wrote: Andrew Reilly wrote: [...] but I don't see a ready equivalent to this with portmaster, hence my dumb script. In particular, I don't think that portmaster can combine the -r and -x flags (depend and exclude), Ummm, why not? It's a little hard to represent in the man page because there are so many flags, but -x is included in the common flags list at the top, and the man page does indicate that -r will take the common flags. You'd have to write it: portmaster -x firefox -r firefox-2.34 (substitute the actual value for the installed firefox port) but it should work. I tried -r and -x few days ago in our last bug hunt in portmaster 2.9, and it did not work. I don't remember what exactly I tried, but I used -i instead and did not investigate if -r and -x is supposed to work together. I can try it again with better attention. There are at least three other ways to do something similar. One would be to use -i instead of -x, another would be an +IGNOREME file. Read the man page for how to use the latter. Yet another way to do what you proposed in the part of your post that I snipped (building based on a list) would have been to do this: pkg_info -q -R firefox-2* list portmaster `cat list` That's probably the simplest way to do what you were trying to accomplish, and would have had the benefit of portmaster caching all the data on up to date dependencies, and building the things in the list in proper dependency order. Sorry to jump in after the fact with this news, but hopefully it will help someone else. [...] Miroslav Lachman ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On 8/24/2009 8:23 PM, Andrew Reilly wrote: Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? I've found pkg_tree to be useful for that. http://www.freebsd.org/cgi/url.cgi?ports/ports-mgmt/pkg_tree/pkg-descr The feature I use the most is pkg_tree -tq which gives a list of all ports that are not depended on by any other ports, i.e. the minimal set to manually reinstall to replicate a set of installed ports on another machine. Jonathan ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
I just rebuilt all of the ports that depended on firefox and I found the following dependencies remained: galeon-2.0.7_1 gnome2-fifth-toe-2.26.3 gnome2-power-tools-2.26.3 mplayerplug-in-3.55_3 muine-0.8.10_1 serpentine-0.7_5 Of these, muine and mplayerplug-in are broken and can't be re-built and serpentine is inheriting the dependency from muine. The two metaports are clearly just inheriting it. I think galeon is the only port that really insists on using firefox. (I have not looked at the Makefile or anything else in the galeon port as I have not used galeon in years and will just delete it. mpalyerplug-in is not marked as broken, but I get the error: c++ -c -o plugin.o -Wall -DXP_UNIX -DMOZ_X11 -I/usr/local/include/firefox/java -I/usr/local/include/firefox/plugin -I/usr/local/include/nspr -I/usr/local/include/firefox -I/usr/local/include/firefox/xpcom -I/usr/local/include/firefox/string -I/usr/local/include/firefox -O2 -fno-strict-aliasing -pipe -D_THREAD_SAFE -I/usr/local/include -D_THREAD_SAFE -I/usr/local/include -I/usr/local/include -DBSD -O2 -fno-strict-aliasing -pipe -Iinclude -fPIC -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -D_THREAD_SAFE -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/pango-1.0 -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/l ocal/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -DGTK_ENABLED Source/plugin.cpp In file included from Source/nsScriptablePeer.h:48, from Source/plugin.h:54, from Source/plugin.cpp:37: Source/nsIScriptableMplayerPlugin.h:41:84: error: macro NS_DEFINE_STATIC_IID_ACCESSOR passed 2 arguments, but takes just 1 Source/nsIScriptableMplayerPlugin.h:254:92: error: macro NS_DEFINE_STATIC_IID_ACCESSOR passed 2 arguments, but takes just 1 In file included from Source/nsScriptablePeer.h:48, from Source/plugin.h:54, from Source/plugin.cpp:37: Source/nsIScriptableMplayerPlugin.h:25: error: function definition does not declare parameters Source/nsIScriptableMplayerPlugin.h:122: error: expected constructor, destructor, or type conversion before 'class' Joe, since you are the maintainer, have you any idea why this is blowing up when built against libxul? -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sun, Aug 23, 2009 at 10:26:25PM -0400, Joe Marcus Clarke wrote: You can set WITH_GECKO=libxul in make.conf, and most of these should go away. I've done that (and installed libxul!) and re-built all of the ports in firefox-2.*/+REQUIRED_BY, and my list is now: alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 gnome-control-center-2.26.0_2 gimp-2.6.6,2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome2-2.26.3 gtkam-gnome-0.1.16.1_1 hamster-applet-2.26.3_1 orca-2.26.3_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 That's a lot shorter than it was before, but still clearly quite long. In most of these I can't see where the firefox dependency is coming from. For instance, the gimp meta-port is still here, but gimp-app has moved over to the libxul-1.9 +REQUIRED_BY list. Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? Cheers, -- Andrew ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Date: Tue, 25 Aug 2009 10:23:59 +1000 From: Andrew Reilly andrew-free...@areilly.bpc-users.org Sender: owner-freebsd-gn...@freebsd.org On Sun, Aug 23, 2009 at 10:26:25PM -0400, Joe Marcus Clarke wrote: You can set WITH_GECKO=libxul in make.conf, and most of these should go away. I've done that (and installed libxul!) and re-built all of the ports in firefox-2.*/+REQUIRED_BY, and my list is now: alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 gnome-control-center-2.26.0_2 gimp-2.6.6,2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome2-2.26.3 gtkam-gnome-0.1.16.1_1 hamster-applet-2.26.3_1 orca-2.26.3_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 That's a lot shorter than it was before, but still clearly quite long. In most of these I can't see where the firefox dependency is coming from. For instance, the gimp meta-port is still here, but gimp-app has moved over to the libxul-1.9 +REQUIRED_BY list. Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? Andrew, How did you sequence the re-builds? I'd guess that gimp-app was re-built after the gimp metaport, so the metaport retained the dependency. If you have portupgrade, I would suggest 'portupgrade -rfx firefox firefox'. portupgrade works by building a dependency graph of the needed ports and builds te tree from the root. This should get rid of all but a handful of ports. It looks like everything in the list should rebuild without the firefox dependency. I had every one of them. I'm now down to just mplayerplug-in because it fails to build against libxul. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Mon, Aug 24, 2009 at 06:18:47PM -0700, Kevin Oberman wrote: Date: Tue, 25 Aug 2009 10:23:59 +1000 From: Andrew Reilly andrew-free...@areilly.bpc-users.org Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? How did you sequence the re-builds? I'd guess that gimp-app was re-built after the gimp metaport, so the metaport retained the dependency. More or less: for i in $(pkg_info -q -o $(cat /var/db/pkg/firefox-2.0.0.20_9,1/+REQUIRED_BY )); do echo $i: cd /usr/ports/$i sudo make build deinstall reinstall clean done If you have portupgrade, I would suggest 'portupgrade -rfx firefox firefox'. portupgrade works by building a dependency graph of the needed ports and builds te tree from the root. This should get rid of all but a handful of ports. I've stopped using portupgrade in favour of portmaster, but I don't see a ready equivalent to this with portmaster, hence my dumb script. In particular, I don't think that portmaster can combine the -r and -x flags (depend and exclude), and when I've done -f -r in combination before, then it seems to build the entire transitive closure of dependencies, rather than just the immediate ones. Hence my question about a tool to manipulate the dependency graph as a graph... Maybe the list will get shorter if I just repeat the rebuild process a few times?... It looks like everything in the list should rebuild without the firefox dependency. I had every one of them. I'm now down to just mplayerplug-in because it fails to build against libxul. That's good to know. It'd be nice to be able to get rid of firefox2, if it's not going to get security patches. Cheers, -- Andrew ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Date: Tue, 25 Aug 2009 12:11:35 +1000 From: Andrew Reilly andrew-free...@areilly.bpc-users.org On Mon, Aug 24, 2009 at 06:18:47PM -0700, Kevin Oberman wrote: Date: Tue, 25 Aug 2009 10:23:59 +1000 From: Andrew Reilly andrew-free...@areilly.bpc-users.org Is there any convenient way to list dependencies hierarchially, rather than the flat set that pkg_info -r provides? How did you sequence the re-builds? I'd guess that gimp-app was re-built after the gimp metaport, so the metaport retained the dependency. More or less: for i in $(pkg_info -q -o $(cat /var/db/pkg/firefox-2.0.0.20_9,1/+REQUIRED_BY )); do echo $i: cd /usr/ports/$i sudo make build deinstall reinstall clean done If you have portupgrade, I would suggest 'portupgrade -rfx firefox firefox'. portupgrade works by building a dependency graph of the needed ports and builds te tree from the root. This should get rid of all but a handful of ports. I've stopped using portupgrade in favour of portmaster, but I don't see a ready equivalent to this with portmaster, hence my dumb script. In particular, I don't think that portmaster can combine the -r and -x flags (depend and exclude), and when I've done -f -r in combination before, then it seems to build the entire transitive closure of dependencies, rather than just the immediate ones. Sadly, there is no good way I know of to avoid this. Hence my question about a tool to manipulate the dependency graph as a graph... That I can help with. It does mean using portupgrade, but not to actually upgrade anything. 'portupgrade -nrfx firefox firefox' will provide a trivially parsable list. If the list is short, cut paste can do it quickly. It's possible that portmaster has a similar capability. Maybe the list will get shorter if I just repeat the rebuild process a few times?... It will, but using the order from the command above will save time. It looks like everything in the list should rebuild without the firefox dependency. I had every one of them. I'm now down to just mplayerplug-in because it fails to build against libxul. That's good to know. It'd be nice to be able to get rid of firefox2, if it's not going to get security patches. Yes, as soon as I can build mplayerplug-in without it, it's history. And none too soon. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Is there any convenient way to list dependencies hierarchially,
rather than the flat set that pkg_info -r provides?
Yes, there is the ports-mgmt/pkg_tree port, and if you want better or
more flexible graphics, you could write a script to swing through
parts of a ports tree, invoke make(1) to find direct dependencies, and
then output the results in, for example, .dot format, so that they can
then be drawn with graphics/graphviz. Obviously, there are other ways
to do this as well. I use the following script to list the origins of
all installed packages that are dependent upon a given package,
according to the given ports tree:
#!/bin/sh
PORTSDIR=${PORTSDIR:-/usr/ports}
if [ `pkg_info -E $1` ]
then
dir1=`pkg_info -oq $1`
for pdir in `pkg_info -aoq`
do
pdepends=`make -C $PORTSDIR/$pdir -V FETCH_DEPENDS -V EXTRACT_DEPENDS
-V PATCH_DEPENDS -V BUILD_DEPENDS -V RUN_DEPENDS -V LIB_DEPENDS`
( echo $pdepends | grep -q -s -e $dir1 ) echo $pdir
#or, if you prefer:
#echo `make -C $PORTSDIR/$pdir -V PKGNAME`
done
else
echo $1 is not a valid package name
exit 1
fi
exit 0
b.
___
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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Mon, Aug 24, 2009 at 07:54:35PM -0700, Kevin Oberman wrote: Date: Tue, 25 Aug 2009 12:11:35 +1000 From: Andrew Reilly andrew-free...@areilly.bpc-users.org Maybe the list will get shorter if I just repeat the rebuild process a few times?... It will, but using the order from the command above will save time. For what it's worth, it took another three iterations, each much shorter than the last. So I'll leave worrying about the dependency graph stuff until the next time... That's good to know. It'd be nice to be able to get rid of firefox2, if it's not going to get security patches. Yes, as soon as I can build mplayerplug-in without it, it's history. And none too soon. Yep: I now have a firefox2-free system. Great stuff. Thanks Joe, all. I wonder, though, doesn't libxul have the same security issues as gecko wrapped up in firefox2? Cheers, -- Andrew ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, Aug 22, 2009 at 08:22:08PM +0200, Martin Wilke wrote: Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Yay! My gnome-based desktop has 46 lines of +REQUIRED_BY in firefox-2.0.0.20_9,1, which is a real pain at the moment, because port-audit won't allow it to be built, thanks to the known vulnerabilities. That makes upgrades with portmaster a chore. Is there an existing fix that everyone but me is using so that the following *don't* depend on firefox-2 on their system? (This is my afore-mentioned +REQUIRD_BY file contents:) gegl-0.0.22_6 gimp-2.6.6,2 gnome2-2.26.3 ufraw-0.15_3 xsane-0.996_1 librsvg2-2.26.0_1 nautilus-2.26.3_1 gnome-panel-2.26.3_1 py26-gnome-desktop-2.26.0_1 file-roller-2.26.3_1,1 gdm-2.26.1_6 gimp-gutenprint-5.1.7_2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome-netstatus-2.26.0_1 gnome-power-manager-2.24.4_5 gnome-system-monitor-2.26.2_1 gnome-system-tools-2.22.2_1 gnome-utils-2.26.0_2,1 hamster-applet-2.26.3_1 libgail-gnome-1.20.1_1 mousetweaks-2.26.3_1 orca-2.26.3_1 py26-gimp-app-2.6.6_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 yelp-2.26.0_1 gtkam-gnome-0.1.16.1_1 tsclient-0.150_5 ImageMagick-6.5.4.10_1 alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 evince-2.26.2_2 gimp-app-2.6.6_3,1 vino-2.26.2_2 graphviz-2.24.0_1 gnome-control-center-2.26.0_2 totem-2.26.3_1 vinagre-2.26.2_1 Cheers, -- Andrew ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Mon, 2009-08-24 at 12:05 +1000, Andrew Reilly wrote: On Sat, Aug 22, 2009 at 08:22:08PM +0200, Martin Wilke wrote: Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Yay! My gnome-based desktop has 46 lines of +REQUIRED_BY in firefox-2.0.0.20_9,1, which is a real pain at the moment, because port-audit won't allow it to be built, thanks to the known vulnerabilities. That makes upgrades with portmaster a chore. Is there an existing fix that everyone but me is using so that the following *don't* depend on firefox-2 on their system? (This is my afore-mentioned +REQUIRD_BY file contents:) You can set WITH_GECKO=libxul in make.conf, and most of these should go away. Joe gegl-0.0.22_6 gimp-2.6.6,2 gnome2-2.26.3 ufraw-0.15_3 xsane-0.996_1 librsvg2-2.26.0_1 nautilus-2.26.3_1 gnome-panel-2.26.3_1 py26-gnome-desktop-2.26.0_1 file-roller-2.26.3_1,1 gdm-2.26.1_6 gimp-gutenprint-5.1.7_2 gnome-applets-2.26.3_1 gnome-games-2.26.3_1 gnome-netstatus-2.26.0_1 gnome-power-manager-2.24.4_5 gnome-system-monitor-2.26.2_1 gnome-system-tools-2.22.2_1 gnome-utils-2.26.0_2,1 hamster-applet-2.26.3_1 libgail-gnome-1.20.1_1 mousetweaks-2.26.3_1 orca-2.26.3_1 py26-gimp-app-2.6.6_1 seahorse-plugins-2.26.2_2 sound-juicer-2.26.1_1 yelp-2.26.0_1 gtkam-gnome-0.1.16.1_1 tsclient-0.150_5 ImageMagick-6.5.4.10_1 alacarte-0.12.1_1 brasero-2.26.3_1 cairo-clock-0.3.2_3 cheese-2.26.3_1 deskbar-applet-2.26.2_1 empathy-2.26.2_1 eog-2.26.3_1 epiphany-2.26.3_3 epiphany-extensions-2.26.1_1 evince-2.26.2_2 gimp-app-2.6.6_3,1 vino-2.26.2_2 graphviz-2.24.0_1 gnome-control-center-2.26.0_2 totem-2.26.3_1 vinagre-2.26.2_1 Cheers, -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
[HEADUP] FreeBSD Gecko's TODO and plan for future
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. 2) or we the FreeBSD Team have to remove all these ports. We know that's really hard but we should not hold vulnerabilities stuff. We hope to get here a bit help from the FreeBSD Gnome Team to make it possible to get some stuff to work with the current libxul version. Current Status: We working currently on Firefox 3.6 (alpha1) [2], Thunderbird 3.0 (beta3) [1], new libxul 1.9.1.2. All 3 are already committed to our repo. [1] a screenshot from tb3 under FreeBSD http://tmp.chruetertee.ch/tb3.0b3.png [2] a screenshot from ff36 under FreeBSD http://tmp.chruetertee.ch/ff36.png A current status can you find here: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO So that's all at the moment, Feedback, Comments are welcome. - - Martin for the FreeBSD Gecko Team - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkqQN08ACgkQdLJIhLHm/OlZ7wCgk6xG3ymevRMf1D/0e9LpEqZ4 vF8An200XdohvNq3nptL4NCBIom+vgPN =SlKU -END PGP SIGNATURE- ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, Aug 22, 2009 at 2:22 PM, Martin Wilke m...@freebsd.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. 2) or we the FreeBSD Team have to remove all these ports. We know that's really hard but we should not hold vulnerabilities stuff. We hope to get here a bit help from the FreeBSD Gnome Team to make it possible to get some stuff to work with the current libxul version. Current Status: We working currently on Firefox 3.6 (alpha1) [2], Thunderbird 3.0 (beta3) [1], new libxul 1.9.1.2. All 3 are already committed to our repo. [1] a screenshot from tb3 under FreeBSD http://tmp.chruetertee.ch/tb3.0b3.png [2] a screenshot from ff36 under FreeBSD http://tmp.chruetertee.ch/ff36.png A current status can you find here: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO So that's all at the moment, Feedback, Comments are welcome. - - Martin for the FreeBSD Gecko Team - -- +---+---+ | PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkqQN08ACgkQdLJIhLHm/OlZ7wCgk6xG3ymevRMf1D/0e9LpEqZ4 vF8An200XdohvNq3nptL4NCBIom+vgPN =SlKU -END PGP SIGNATURE- ___ freebsd-gn...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org I just have one question when has xulrunner been unsupported upstream considering that xulrunner 1.9.1 was released when firefox 3.5.2 was teh last release of xulrunner 1.9.x alpha was august 22end yes it's development but it's still supported. upstream ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, 2009-08-22 at 20:22 +0200, Martin Wilke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. The debate is still on-going (due to a11y concerns), but it looks like WebKit is going to be the de facto standard in GNOME 2.28. That should greatly reduce the number of ports that require Gecko. As it stands now, just about all of the GNOME ports build against libxul, and the firefox Gecko provider can simply be removed. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, Aug 22, 2009 at 3:12 PM, J.-P. Klodzinski j...@gmx.org wrote: matt donovan wrote: On Sat, Aug 22, 2009 at 2:22 PM, Martin Wilke m...@freebsd.org wrote: Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. 2) or we the FreeBSD Team have to remove all these ports. We know that's really hard but we should not hold vulnerabilities stuff. We hope to get here a bit help from the FreeBSD Gnome Team to make it possible to get some stuff to work with the current libxul version. Current Status: We working currently on Firefox 3.6 (alpha1) [2], Thunderbird 3.0 (beta3) [1], new libxul 1.9.1.2. All 3 are already committed to our repo. [1] a screenshot from tb3 under FreeBSD http://tmp.chruetertee.ch/tb3.0b3.png [2] a screenshot from ff36 under FreeBSD http://tmp.chruetertee.ch/ff36.png A current status can you find here: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO So that's all at the moment, Feedback, Comments are welcome. - Martin for the FreeBSD Gecko Team ___ freebsd-gn...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org I just have one question when has xulrunner been unsupported upstream considering that xulrunner 1.9.1 was released when firefox 3.5.2 was teh last release of xulrunner 1.9.x alpha was august 22end yes it's development but it's still supported. upstream ___ 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 Hi, I think he means www/xulrunner, based on 1.8.0 (http://www.freshports.org/www/xulrunner/) is no longer supported und should get removed from the tree. Your mentioned xulrunner 1.9.x is still supported and inside the ports-tree under www/libxul, which will not get removed. (http://www.freshports.org/www/libxul/) /BR Ah ok since I know that libxul is a single library. hence why I got a bit confused since I knew xulrunner is still supported jsut not 1.8.x ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
matt donovan wrote: On Sat, Aug 22, 2009 at 2:22 PM, Martin Wilke m...@freebsd.org wrote: Howdy Guys, The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. * www/mozilla is 5 year old now, no longer supported by upstream, and has many many vulnerabilities. We can use www/seamonkey. * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. * www/xulrunner is old and was replaced by www/libxul. We should not hold any old Gecko stuff. Also it's not longer supported by upstream: https://wiki.mozilla.org/XULRunner:Roadmap Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. Also www/firefox has a lot of vulnerabilities. We should www/firefox mark FORBIDDEN at this time gives no fixes for the latest securtiy reports. We see here 2 ways: 1) The Gnome Team (not the FreeBSD Gnome Team) take time and move all his stuff to libxul. 2) or we the FreeBSD Team have to remove all these ports. We know that's really hard but we should not hold vulnerabilities stuff. We hope to get here a bit help from the FreeBSD Gnome Team to make it possible to get some stuff to work with the current libxul version. Current Status: We working currently on Firefox 3.6 (alpha1) [2], Thunderbird 3.0 (beta3) [1], new libxul 1.9.1.2. All 3 are already committed to our repo. [1] a screenshot from tb3 under FreeBSD http://tmp.chruetertee.ch/tb3.0b3.png [2] a screenshot from ff36 under FreeBSD http://tmp.chruetertee.ch/ff36.png A current status can you find here: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO So that's all at the moment, Feedback, Comments are welcome. - Martin for the FreeBSD Gecko Team ___ freebsd-gn...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-gnome To unsubscribe, send any mail to freebsd-gnome-unsubscr...@freebsd.org I just have one question when has xulrunner been unsupported upstream considering that xulrunner 1.9.1 was released when firefox 3.5.2 was teh last release of xulrunner 1.9.x alpha was august 22end yes it's development but it's still supported. upstream ___ 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 Hi, I think he means www/xulrunner, based on 1.8.0 (http://www.freshports.org/www/xulrunner/) is no longer supported und should get removed from the tree. Your mentioned xulrunner 1.9.x is still supported and inside the ports-tree under www/libxul, which will not get removed. (http://www.freshports.org/www/libxul/) /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: [HEADUP] FreeBSD Gecko's TODO and plan for future
Martin Wilke m...@freebsd.org wrote: Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. ... * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. ... Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. So, if I am understanding this correctly, it's proposed to replace nvu with an updated kompozer, which to judge from the name is part of KDE. Thus Gnome acquires a dependency on KDE by way of firefox/gecko? This does not seem like a Good Thing (TM). ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, 22 Aug 2009 15:52:43 -0500, per...@pluto.rain.com wrote: Martin Wilke m...@freebsd.org wrote: Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. ... * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. ... Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. So, if I am understanding this correctly, it's proposed to replace nvu with an updated kompozer, which to judge from the name is part of KDE. Thus Gnome acquires a dependency on KDE by way of firefox/gecko? This does not seem like a Good Thing (TM). Why don't you check what kompozer is first? ;-) Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, Aug 22, 2009 at 5:35 PM, Jeremy Messenger me...@cox.net wrote: On Sat, 22 Aug 2009 15:52:43 -0500, per...@pluto.rain.com wrote: Martin Wilke m...@freebsd.org wrote: Background: We have a lot of old stuff on the portstree and it's time to cleanup old stuff. ... * www/nvu last official release was in 2005, no longer supported, and also some vulnerabilities. We have www/kompozer which also need an update to get this unbroken. ... Problems which we have to solve: Some Gnome ports need www/firefox to build and work, but unfortunately firefox2 isn't longer supported by the Mozilla Foundation. So, if I am understanding this correctly, it's proposed to replace nvu with an updated kompozer, which to judge from the name is part of KDE. Thus Gnome acquires a dependency on KDE by way of firefox/gecko? This does not seem like a Good Thing (TM). Why don't you check what kompozer is first? ;-) Cheers, Mezz -- me...@cox.net - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@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 kompozer is NVU KompoZer is an unoffical bugfix/update aka a fork ___ 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: [HEADUP] FreeBSD Gecko's TODO and plan for future
On Sat, Aug 22, 2009 at 3:22 PM, Martin Wilkem...@freebsd.org wrote: The FreeBSD Gecko Team will let you know what the plans for the future are and on what we are currently working. Goals: * Removal of mozilla, nvu, xulrunner and firefox2. * www/firefox35 should be moved to www/firefox. * The options USE_GECKO mozilla nvu xulrunner and firefox will be also removed. Would it be possible to manage to build firefox35 without Python? I'm attempting to build a skinny desktop environment based on Xfce and reducing the number of dependencies of firefox would be very desirable. -- My preferred quotation of Robert Louis Stevenson is You cannot make an omelette without breaking eggs. Not because I like the omelettes, but because I like the sound of eggs being broken. ___ 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
