Re: how to upgrade ports that depend on openssl-stable?
On Fri, Sep 19, 2008 at 12:08:15AM -0500, David J Brooks wrote: I keep running into this error: === openssl-stable-0.9.7m_1 Conflicts with version in the base. *** Error code 1 OpenSSL is included in FreeBSD in the base system. The port you're trying to install requires a newer version of OpenSSL than what's in the base system. You need to define WITH_OPENSSL_BASE=yes in your /etc/make.conf. This should make the port build/install successfully, and will overwrite the OpenSSL installation in the base system. You will also need to set WITHOUT_OPENSSL=true in /etc/src.conf (assuming this is FreeBSD 7.x), to ensure the next time you build/install world, that you do not bother building the base version of OpenSSL, and instead continue to rely on the port version. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to upgrade ports that depend on openssl-stable?
On Thu, Sep 18, 2008 at 11:27:32PM -0700, Jeremy Chadwick wrote: On Fri, Sep 19, 2008 at 12:08:15AM -0500, David J Brooks wrote: I keep running into this error: === openssl-stable-0.9.7m_1 Conflicts with version in the base. *** Error code 1 OpenSSL is included in FreeBSD in the base system. The port you're trying to install requires a newer version of OpenSSL than what's in the base system. You need to define WITH_OPENSSL_BASE=yes in your /etc/make.conf. This should make the port build/install successfully, and will overwrite the OpenSSL installation in the base system. You will also need to set WITHOUT_OPENSSL=true in /etc/src.conf (assuming this is FreeBSD 7.x), to ensure the next time you build/install world, that you do not bother building the base version of OpenSSL, and instead continue to rely on the port version. One other thing I forgot to mention: You will need to rebuild all ports reliant on SSL (this may be hard to determine reliably), as well as all base system utilities reliant on SSL (make world will suffice for this), as there will very likely be a library version mismatch between the old base OpenSSL and the port version of OpenSSL. There's a chance you won't have to do this (I installed the port like you said and everything still works), but I would recommend you not take any chances. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: VirtualBox looks for FreeBSD developer
On Thu, Sep 11, 2008 at 12:17:53PM +0200, Klaus Espenlaub wrote: Hi, Torfinn Ingolfsen wrote: On Mon, Sep 8, 2008 at 3:22 PM, Klaus Espenlaub [EMAIL PROTECTED] wrote: #include disclaimer I speak for myself and nobody else. I do not claim that I in any way represent FreeBSD. freebsd is yet another kernel for which the VirtualBox devs would have to figure out how to safely achieve a few things normal applications don't ever need. Like dealing with physical memory, getting along with the scheduler and stuff like that. It's also true that the written documentation in VirtualBox about this area leaves something to be desired - again a manpower problem. It is easy for me as an outsider to see that this can be viewed from the opposite angle: VirtualBox is just another virtualization solution for FreeBSD. We are sorry that the VirtualBox team can't find any time to provide the necessary documentation. Currently FreeBSD don't have any developers with enough free time to figure things out from the documentation available now. You see - it is simply a manpower problem. I think you could better ask for help on [EMAIL PROTECTED] as there aren't too many kernel developers reading ports@ is guess. pgpHcsBd680hn.pgp Description: PGP signature
Re: FreeBSD Port: clamav-0.94_1
On Fri, Sep 19, 2008 at 12:40:35PM +0800, Snopy Land wrote: Hi, My server version is freebsd6.2 amd64. I have installed clamav to scan my ^^^ According to http://www.freebsd.org/security/ it is not supported any more. Consider upgrading your base system (as opposed to ports) as well. incoming mail. Everything works smoothly for several years. Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest version). The procedure used (from the original mail): 1. run make deinstall to deinstall the clamav version of 0.92 2. Modify /usr/ports-supfile (to make sure security port can be download from a correct default host) *default host=ftp.tw.freebsd.org ports-security --- remark ports-all, and enable the ports-security only ^^ That is not a good idea, I think. 3. cd /usr ; run cvsup -g -L 2 ports-supfile 4. check /usr/port/security/clamav port is updated 5. cd /usr/port/security/clamav 6. run make install clean There is no error message found in the whole process, however, I cannot find the file of clamd, clamscan freshclam. The previous version of these file can be found in /usr/local/sbin and /usr/local/bin After redo the upgrade process, I find there are some files under /usr/local/bin and /usr/local/sbin but the file name is differenet. ls -ltr /usr/local/bin -r-xr-xr-x 1 root wheel80624 Sep 19 11:07 amd64-portbld-freebsd6.2-sigtool -r-xr-xr-x 1 root wheel87944 Sep 19 11:07 amd64-portbld-freebsd6.2-freshclam -r-xr-xr-x 1 root wheel51968 Sep 19 11:07 amd64-portbld-freebsd6.2-clamscan -r-xr-xr-x 1 root wheel52592 Sep 19 11:07 amd64-portbld-freebsd6.2-clamdscan -r-xr-xr-x 1 root wheel28272 Sep 19 11:07 amd64-portbld-freebsd6.2-clamconf -r-xr-xr-x 1 root wheel 1103 Sep 19 11:07 amd64-portbld-freebsd6.2-clamav-config ls -ltr /usr/local/sbin -r-xr-xr-x 1 root wheel67536 Sep 19 11:07 amd64-portbld-freebsd6.2-clamd Are these files are the same as the file of clamd, freshclam and clamscan. If yes, can I create symbolic link for these file so that I can keep my old setting? (i.e run /usr/local/sbin/clamd -c /usr/local/etc/clamd.conf, and run /usr/local/bin/freshclam --quiet in the cronjob). How many configuration files location should I change ? Yes, these files are the same. You have run into this problem because you have not updated the whole tree, namely ports/Mk* directory. There was a change which is responsible for fixing these ugly names. FWIW, from the /usr/share/examples/cvsup/ports-supfile: # These are the individual collections that make up ports-all. If you # use these, be sure to comment out ports-all above. # # Be sure to ALWAYS cvsup the ports-base collection if you use any of the # other individual collections below. ports-base is a mandatory collection # for the ports collection, and your ports may not build correctly if it # is not kept up to date. #ports-base Good luck! Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
CALL FOR TEST Qt 4.4.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everybody! Yesterday Qt 4.4.2 was released, area51 is already updated, and I would like some testers before we commit it to the Ports tree after the freeze. You can find the changelog here: http://trolltech.com/developer/resources/notes/changes/changes-4.4.2 Note on area51: You now need subversion to checkout area51, svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51 Happy Testing. Regards Martin - -- +---+---+ | PGP: 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ: 169139903 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjTZ0sACgkQFwpycAVoI1OxyQCglTwiiGJCcFLfkhL73wnnPDyE OO0An0jZhIGjA9C0wlsYrNuEdK0Ivlwf =noBp -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: teTeX/TeXLive: powerdot still missing ...
On Thu, Sep 18, 2008 at 02:03:01PM +, O. Hartmann wrote: Still using teTeX, but as we all know, development has been canceld by Thomas Esser. I'm looking for a working 'powerdot' which is part of TeXLive now, but there is no TeXLive-port available for FreeBSD. Searching for that matter brings up some informations released a year ago and I'm wondering about the fact that there is no support for FreeBSD. Is there a workaround or 'master plan' how to bring TeXLive to a FreeBSD bx in a clean way? Can TeXLive coexists with teTeX. Not about porting TeXLive to FreeBSD actually. After a quick look at 'powerdot' class I can suggest you using 'beamer' as a workaround. It is in the teTeX. Porting of TeXLive is a todo anyway, I think. Alexey. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: teTeX/TeXLive: powerdot still missing ...
2008/9/19 Alexey Shuvaev [EMAIL PROTECTED]: On Thu, Sep 18, 2008 at 02:03:01PM +, O. Hartmann wrote: Still using teTeX, but as we all know, development has been canceld by Thomas Esser. I'm looking for a working 'powerdot' which is part of TeXLive now, but there is no TeXLive-port available for FreeBSD. Searching for that matter brings up some informations released a year ago and I'm wondering about the fact that there is no support for FreeBSD. Is there a workaround or 'master plan' how to bring TeXLive to a FreeBSD bx in a clean way? Can TeXLive coexists with teTeX. Not about porting TeXLive to FreeBSD actually. After a quick look at 'powerdot' class I can suggest you using 'beamer' as a workaround. or ConTeXT which provides support for FreeBSD. Regards -- Diego Depaoli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: teTeX/TeXLive: powerdot still missing ...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 O. Hartmann wrote: | Still using teTeX, but as we all know, development has been canceld by | Thomas Esser. I'm looking for a working 'powerdot' which is part of | TeXLive now, but there is no TeXLive-port available for FreeBSD. | Searching for that matter brings up some informations released a year | ago and I'm wondering about the fact that there is no support for FreeBSD. | Is there a workaround or 'master plan' how to bring TeXLive to a FreeBSD | bx in a clean way? Can TeXLive coexists with teTeX. | | Thank you very much for your patience ... Hi Oliver, I currently have a local working installation of TeXLive. However, there are a few problems which prevent me to commit the port to the ports tree. I am planning to gather feedback and do something about it in the near future, so stay tuned :) | Regards, Best regards, | Oliver - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjTkLIACgkQwMJqmJVx9462NwCdGOrDy4w4O5NJwZ/MxdgyFj+d ZasAnA8HKzvW7A/dI1OoibTuTQ37TaLa =KB/4 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: clamav-0.94_1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Sep 19, 2008 at 12:40:35PM +0800, Snopy Land wrote: Hi, My server version is freebsd6.2 amd64. I have installed clamav to scan my incoming mail. Everything works smoothly for several years. Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest version). There is no error message found in the whole process, however, I cannot find the file of clamd, clamscan freshclam. The previous version of these file can be found in /usr/local/sbin and /usr/local/bin I have posted my problem in the mailling list of freebsd-ports, however, I cannot get any hints. After redo the upgrade process, I find there are some files under /usr/local/bin and /usr/local/sbin but the file name is differenet. ls -ltr /usr/local/bin -r-xr-xr-x 1 root wheel80624 Sep 19 11:07 amd64-portbld-freebsd6.2-sigtool -r-xr-xr-x 1 root wheel87944 Sep 19 11:07 amd64-portbld-freebsd6.2-freshclam -r-xr-xr-x 1 root wheel51968 Sep 19 11:07 amd64-portbld-freebsd6.2-clamscan -r-xr-xr-x 1 root wheel52592 Sep 19 11:07 amd64-portbld-freebsd6.2-clamdscan -r-xr-xr-x 1 root wheel28272 Sep 19 11:07 amd64-portbld-freebsd6.2-clamconf -r-xr-xr-x 1 root wheel 1103 Sep 19 11:07 amd64-portbld-freebsd6.2-clamav-config ls -ltr /usr/local/sbin -r-xr-xr-x 1 root wheel67536 Sep 19 11:07 amd64-portbld-freebsd6.2-clamd Are these files are the same as the file of clamd, freshclam and clamscan. If yes, can I create symbolic link for these file so that I can keep my old setting? (i.e run /usr/local/sbin/clamd -c /usr/local/etc/clamd.conf, and run /usr/local/bin/freshclam --quiet in the cronjob). How many configuration files location should I change ? Thanks. This same problem happened with another user, and the cause was his ports tree and autotools ports are not up-to-date. Please, update your ports tree, update all autotools ports (automake, autoconf, libtool) and rebuild clamav. Thanks - -- Renato Botelho garga @ FreeBSD.org garga @ freebsdbrasil.com.br GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc The one good thing about repeating your mistakes is that you know when to cringe. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjTjnEACgkQ6CRbiSJE7amXzwCePlC+uU715DPcmIlIxYfW5nJM XloAoLGXwcWWYPniW2VIXlv5fQU9JJns =VOj/ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: py25-wxPython-2.8.7.1_1
Hello, The version in the ports tree is a bit dated (Nov. 2007). Any chance we can get an update (current is 2.8.8.1)? Thanks. -- Regards, Ghirai. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
www/vee
I am the author of www/vee, and when checking to see if it's been upgraded to the latest I found out that there was no longer a maintainer for this port. http://www.freshports.org/www/?page=19 I am interested in getting the latest version into ports, and am willing to become port maintainer for it - if someone would kindly point me to the documentation describing how to do such a thing. The vee site is: http://www.0x743.com/vee/ Cheers, Brett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/vee
On Fri, Sep 19, 2008 at 11:58:08AM -0500, B. Estrade wrote: I am the author of www/vee, and when checking to see if it's been upgraded to the latest I found out that there was no longer a maintainer for this port. http://www.freshports.org/www/?page=19 I am interested in getting the latest version into ports, and am willing to become port maintainer for it - if someone would kindly point me to the documentation describing how to do such a thing. The vee site is: http://www.0x743.com/vee/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Also, reading through /usr/ports/Mk/* is a good idea if you ever get stuck. Lastly, this list is also helpful in case you have questions that are not answered with the above resources. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] CALL FOR TEST Qt 4.4.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yep we also documented that today, https://kf.athame.co.uk/access.php On Fri, Sep 19, 2008 at 07:40:03PM +0200, Dorian Büttner wrote: Martin Wilke schrieb: Note on area51: You now need subversion to checkout area51, svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51 Anything else remains the same? 3. Choose a partition for the area51 repository checkout. I personally use /var, but you can use what you want. 4. If you use /var (or use your path here) then # cd /var 5. This creates a folder area51 into /var with checked out repository. # cvs -d:ext:[EMAIL PROTECTED]:/home/kde-freebsd co area51 6. If you use /var (or use your path here) then # mount -t unionfs /var/area51 /usr/ports You have now area51 repository on top of your existing ports tree. Use your ports tree now as usual. 7. Install / update QT 4 first. 8. Install KDE 4 ports you want. You can start with /usr/ports/x11/kdebase4 That is all. When you want to use your unmodified original ports tree just # umount /usr/ports and everything is like before. Of course do not downgrade / uninstall the new installed ports and run KDE 4 only with your test user accoun Thanks, Dorian - -- +---+---+ | PGP: 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ: 169139903 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkjUAlgACgkQFwpycAVoI1MVYwCbBy/ZpiJQHhl+ymzrcx+pWPsg EmMAn2si+zExz69BDKS/inDBzl3mj6II =E3/p -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [kde-freebsd] CALL FOR TEST Qt 4.4.2
Martin Wilke schrieb: Note on area51: You now need subversion to checkout area51, svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51 Anything else remains the same? 3. Choose a partition for the area51 repository checkout. I personally use /var, but you can use what you want. 4. If you use /var (or use your path here) then # cd /var 5. This creates a folder area51 into /var with checked out repository. # cvs -d:ext:[EMAIL PROTECTED]:/home/kde-freebsd co area51 6. If you use /var (or use your path here) then # mount -t unionfs /var/area51 /usr/ports You have now area51 repository on top of your existing ports tree. Use your ports tree now as usual. 7. Install / update QT 4 first. 8. Install KDE 4 ports you want. You can start with /usr/ports/x11/kdebase4 That is all. When you want to use your unmodified original ports tree just # umount /usr/ports and everything is like before. Of course do not downgrade / uninstall the new installed ports and run KDE 4 only with your test user accoun Thanks, Dorian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OPTIONS handling doesn't seem to work fully in dependencies anymore
Alex Dupre wrote:
The attached patch should solve this erratic behavior.
Another quick patch, that removes handling OPTIONS as a special case.
--
Alex Dupre
--- bsd.port.mk.orig2008-09-19 23:15:37.0 +0200
+++ bsd.port.mk 2008-09-19 23:29:30.0 +0200
@@ -3229,17 +3229,6 @@
.endif
-#
-# Do preliminary work to detect if we need to run the config
-# target or not.
-#
-
-.if (!defined(OPTIONS) || defined(CONFIG_DONE) || \
- defined(PACKAGE_BUILDING) || defined(BATCH))
-_OPTIONS_OK=yes
-.endif
-
-
# The following are used to create easy dummy targets for
# disabling some bit of default target behavior you don't want.
# They still check to see if the target exists, and if so don't
@@ -4114,7 +4103,7 @@
_SANITY_SEQ= ${_CHROOT_SEQ} pre-everything check-makefile check-categories \
check-makevars check-desktop-entries
check-depends \
check-deprecated check-vulnerable
buildanyway-message \
- options-message
+ options-message config-conditional
_FETCH_DEP=check-sanity
_FETCH_SEQ=fetch-depends pre-fetch pre-fetch-script \
do-fetch post-fetch post-fetch-script
@@ -4165,12 +4154,8 @@
.for target in extract patch configure build install package
-.if !target(${target}) defined(_OPTIONS_OK)
+.if !target(${target})
${target}: ${${target:U}_COOKIE}
-.elif !target(${target})
-${target}: config-conditional
- @cd ${.CURDIR} ${MAKE} CONFIG_DONE=1 ${__softMAKEFLAGS}
${${target:U}_COOKIE}
-.elif target(${target}) defined(IGNORE)
.endif
.if !exists(${${target:U}_COOKIE})
@@ -5936,7 +5921,7 @@
.if !target(config-conditional)
config-conditional:
-.if defined(OPTIONS)
+.if defined(OPTIONS) !defined(PACKAGE_BUILDING) !defined(BATCH)
.if exists(${OPTIONSFILE})
# scan saved options and invalidate them, if the set of options does not match
@. ${OPTIONSFILE}; \
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/vee
On Fri, Sep 19, 2008 at 01:26:31PM -0400, Wesley Shields wrote: On Fri, Sep 19, 2008 at 11:58:08AM -0500, B. Estrade wrote: I am the author of www/vee, and when checking to see if it's been upgraded to the latest I found out that there was no longer a maintainer for this port. http://www.freshports.org/www/?page=19 I am interested in getting the latest version into ports, and am willing to become port maintainer for it - if someone would kindly point me to the documentation describing how to do such a thing. The vee site is: http://www.0x743.com/vee/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Also, reading through /usr/ports/Mk/* is a good idea if you ever get stuck. Lastly, this list is also helpful in case you have questions that are not answered with the above resources. -- WXS Okay. So I followed the instructions on updating at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/port-upgrading.html, and during the process updated the checksum file with 'make makesum' and ran the suggested install/deinstall/reinstall/etc tests. Everything worked fine, so I sent in the result of 'diff -ruN vee.bak vee' in through send-pr. So is that about it? Also, I mentioned in the report that I'd like to be the maintainer for the port, but would like to reiterate it. Thanks - this was pretty fun and the replies I got were very helpful. Cheers, Brett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/vee
On Fri, Sep 19, 2008 at 06:23:36PM -0500, B. Estrade wrote: On Fri, Sep 19, 2008 at 01:26:31PM -0400, Wesley Shields wrote: On Fri, Sep 19, 2008 at 11:58:08AM -0500, B. Estrade wrote: I am the author of www/vee, and when checking to see if it's been upgraded to the latest I found out that there was no longer a maintainer for this port. http://www.freshports.org/www/?page=19 I am interested in getting the latest version into ports, and am willing to become port maintainer for it - if someone would kindly point me to the documentation describing how to do such a thing. The vee site is: http://www.0x743.com/vee/ http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Also, reading through /usr/ports/Mk/* is a good idea if you ever get stuck. Lastly, this list is also helpful in case you have questions that are not answered with the above resources. -- WXS Okay. So I followed the instructions on updating at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/port-upgrading.html, and during the process updated the checksum file with 'make makesum' and ran the suggested install/deinstall/reinstall/etc tests. Everything worked fine, so I sent in the result of 'diff -ruN vee.bak vee' in through send-pr. So is that about it? Also, I mentioned in the report that I'd like to be the maintainer for the port, but would like to reiterate it. Provided it passes the tests that a committer will put your update through, then yes. We are currently in a freeze for the upcoming releases so please be patient as the kind of update you have prepared will have to wait until the tree is thawed. Thanks - this was pretty fun and the replies I got were very helpful. Your welcome, and welcome to the club. :) -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Does anyone know nginx's www path
Since I am trying to get this setup for a developer machine and I can't get to the default index.html. and it seems that the pid file is not created either with the port. All I get with a default nginx install is a 404 error ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
