Is there a reason that the gnome 2 ports don't use the conflicts
mechanism to avoid completely hosing an existing gnome 2 install? On
Friday I came across a gimp script-fu which would slice an image into
pieces and output html that rendered the complete image as a
table. But it was written in
On 05-Feb-2006 Christopher Sean Hilton wrote:
Is there a reason that the gnome 2 ports don't use the conflicts
mechanism to avoid completely hosing an existing gnome 2 install? On
Friday I came across a gimp script-fu which would slice an image into
pieces and output html that rendered the
On Sun, Feb 05, 2006 at 02:54:07PM -0600, Conrad Sabatier wrote:
On 05-Feb-2006 Christopher Sean Hilton wrote:
Is there a reason that the gnome 2 ports don't use the conflicts
mechanism to avoid completely hosing an existing gnome 2 install? On
[snip]
Let me be more clear because I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greetings,
I run Apache 1.3+ssl on a computer that I'm installing Gnome 2.12.2 via
the meta-port in x11/gnome2. As part of that install, it builds and
installs www/gnome-user-share. *That* port forces the www/apache20 port
upon me.
Since my
,
-Wes
The only gnome port I can find that as that port as a dependency is
x11/gnome2-power-tools, not x11/gnome2.
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
and
|installs www/gnome-user-share. *That* port forces the www/apache20 port
|upon me.
|[snip]
|
| The only gnome port I can find that as that port as a dependency is
| x11/gnome2-power-tools, not x11/gnome2.
|
| -Mike
You're right. Originally when I installed Gnome2, I used the
gnome2-lite meta-port
and
|installs www/gnome-user-share. *That* port forces the www/apache20 port
|upon me.
|[snip]
|
| The only gnome port I can find that as that port as a dependency is
| x11/gnome2-power-tools, not x11/gnome2.
|
| -Mike
You're right. Originally when I installed Gnome2, I used the
gnome2-lite
I recently tried to update my xscreensaver-gnome port from
4.15_2 to 4.16. After the usual amount of churning, it
died with the following error:
---
In file included from phosphor.c:34:
/usr/local/include/util.h:95: error: syntax error before '/' token
In file included from phosphor.c:34:
/usr
New install last night, cvsup'd main and ports did make world, and now I'm
trying to build /usr/ports/x11-gnome.
It dies in /usr/ports/lang/librep trying to run the repdoc command it just
built, which segfaults.
Sugestiosn?
--
They that would give up essential liberty for temporary safety
