Gnome port forcing Apache 2.0 on me during install
-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 version of Apache conflicts with the version it wants, portmanager dutifully uninstalls my version and installs 2.0 in an unconfigured state. Seems to me there should be some sort of warning, opt-out choice, or choice to pick a different http server (if gnome-user-share permits it) before doing this to a user. There are a lot of http servers listed and maintained in the ports tree. Are my only options to either suck it up and configure Apache 2.0 for my ~ machine, or ditch gnome-user-share and tell portmanager to never install it so I can run the web server I want? Cheers, - -Wes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iQIVAwUBQ6G2p4rq8W17hxGfAQh1Gg//VkWExdYQGrR4rKjHjaK6G8t7sxi5CNgL JTnq55ihSzK6PK40GuHn2UIhfXFm7kY3lst7GSkN2QxtyhHRRyOWM6Z3+pOm6G6q +L3RUmpqDtqJP5AeyIJcK7LPvgyRX2nRT1DEcbwNfxGWd5XVJhvK7pOASL+MElq7 xrjcBaaZgVuLXa0lv2fdd8EXiuE/xRGWPw0vTc/AdXJS4B/koa6iOVXism20g6ML 1uJMdHM3N+hvi5+NAPaKauDUDG2+DbmfDLBxJXS/S+Y24YrmCDYOSxlpgvW9os4L dyeChyCBL0TV75CIM+CuYp3oSXfIkFwHgzhFqEyDDkQj2GUR3G1o/yDoqObaYj5y 2/4N+7DLGeaMxwmGZLxIYvopyqmW/mAPnj2QuNlJLPQY6kywllwsBt0xi9ET18Qo Fof2vS8ptxbSNPNjNrcgikonyKe2tksOXv4ixOw3p4Ps6rY9ANJl1MkHZZ7ELhdd oigU9/P5bGNbT9EEvBOac6OaVuLyin0g/mZObA9xuNNnVyzQQCfNhRcwct5U/UkM v/45PMmayDHGMBG4NRgg6fOps5+JYNduZk2InEYyHYCO3DDZC0lrYh3comQVQ4iY 2SnCw+WQfo9xTpEOwMrxK+WTuF1IaQ2HNsyp7oVzYVfrMWMX91/n8Yj0A+teVS2w uUlwJypBMf4= =0eM8 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gnome port forcing Apache 2.0 on me during install
On Thursday 15 December 2005 10:32, Wes Santee wrote: 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 version of Apache conflicts with the version it wants, portmanager dutifully uninstalls my version and installs 2.0 in an unconfigured state. Seems to me there should be some sort of warning, opt-out choice, or choice to pick a different http server (if gnome-user-share permits it) before doing this to a user. There are a lot of http servers listed and maintained in the ports tree. Are my only options to either suck it up and configure Apache 2.0 for my ~ machine, or ditch gnome-user-share and tell portmanager to never install it so I can run the web server I want? Cheers, -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 mail to [EMAIL PROTECTED]
Re: Gnome port forcing Apache 2.0 on me during install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Michael C. Shultz wrote: | On Thursday 15 December 2005 10:32, Wes Santee wrote: | |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. |[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. It lists other ports to install to get the more full featured Gnome. After I while I removed the gnome2-lite port and installed the gnome2 full port since I was slowly adding the add-on ports it mentioned anyway. I assumed the bits I had already added were part of the full port. Guess I can just delete the port and be done with it. That solution doesn't really address the larger issue of a port that will toss your HTTP server out without so much as a how-do-you-do, but at least I can go back to my known configuration easily enough. Cheers, - -Wes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) iQIVAwUBQ6HHz4rq8W17hxGfAQhZjQ/9HDsPaj5efTxIG2LTXxIDgU/f1Zr47XKG /Z0rV+VJ5VLhNfNnwy67cFJ2OgriucgToY0BbN0KjWk+uvRPaLV8w2ca/UvHp6HX IY4VvfCyrx0QIpjKHhB4aCBjcHy8zvWCnvNlUriUzM26dnZ38Vs2gvKgkcBPmVwH 9GvqX/dPk5r0MnOA8FlfszWFfuLvLZFUTBbd3ZxCE7HlFa4JdhWLm5oC50KqG1Wt +PzIjwundw3HLr/v9SaVEP1KYngpFQbL9e0VzxXEv1L+1GEwQpv2zeNs9yU/qUzK ny/tH7L80XZ36n/pNPwfMTmPDIJY4IR9GcWI1RUmHFrdf7h3OglA79Ucdf+JTLpT UJt05cqW4wtVcyqnWzYY6rgul4ehCD79+OOiZEJwq6xBbsAZtkuLg0G4p6dsrOKp RLqJ3XylIzxFQK6JvXfs2lPFkygxk40iq31+cOU0z/cfM9Z27+LoXy8A8ct7SjDE OiV9etK5I6q8nXCKfRxzHGl+fvfhIdjltKpaqxdj2PBFhl7UkE88azgElscxw5QD HTMLCj0eJQB+h4xFd4BV4QduZZFnng3P2ArtDAEA9Eg3BPa5JwnktpnXo4UYsdRP 4p6XcUL03xztxce7xqzfLBEMujSkvkoUH+gEK0omiRYcbk18MyFWCeW2ZCMVWIGN HZKDvlqpdMA= =752p -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Gnome port forcing Apache 2.0 on me during install
On Thursday 15 December 2005 11:45, Wes Santee wrote:
Michael C. Shultz wrote:
| On Thursday 15 December 2005 10:32, Wes Santee wrote:
|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.
|[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. It lists other ports to install to get the more
full featured Gnome. After I while I removed the gnome2-lite port and
installed the gnome2 full port since I was slowly adding the add-on
ports it mentioned anyway. I assumed the bits I had already added were
part of the full port.
Guess I can just delete the port and be done with it. That solution
doesn't really address the larger issue of a port that will toss your
HTTP server out without so much as a how-do-you-do, but at least I can
go back to my known configuration easily enough.
Cheers,
-Wes
Since apache seems very critical to you maybe adding
IGNORE|www/apache*| to /usr/local/etc/portmanager/pm-020.conf
would be a good idea, it would stop surprises.
When you know you want to upgrade apache then comment out
that line and do a portmanager www/apache{version}, just a suggestion...
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
