Re: redports.org - The public FreeBSD ports development infrastructure
On 03.01.2012 22:32, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/29/11 6:44 AM, Bernhard Froehlich wrote: Hi Porters! I am happy to announce that redports.org has finally reached the point where I think It's safe to be used by everybody! In case you never heard of it before redports is the result of an idea born at EuroBSDCon 2011 in Karlsruhe to give Port Maintainers and Port Committers a public service to test their new ports or ports patches during development or before submitting a ports PR. [...] Wow! Stellar job, Bernhard, and I'm looking forward to using redports.org for fixing ports that are broken under clang. Hope you don't want to do that today because during the night the current building machine paniced and needs someone power cycling it. I will do this in the evening so no builds today :( It looks like I could get some hardware from portmgr so hopefully more hardware and redundancy is available soon. I noticed one minor typo on https://redports.org/buildgroups: automaticaly -> automatically Thanks, it's fixed now! -- Bernhard Froehlich http://www.bluelife.at/ ___ 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: x11/nvidia-driver: crash with FreeBSD 9.0-STABLE/amd64 when module loaded via /boot/loader.conf
On 2012/01/03 at 18:15, "O. Hartmann" wrote: > > On one of my FreeBSD 9.0 boxes running FreeBSD 9.0-STABLE/amd64 (CLANG > built), equipted with a nVidia GT760Ti graphics board, loading the > nvidia module via /boot/loader.conf results in a page fault with random > error messages before rebooting. > > Booting the box without the nvidia.ko module loaded in he preboot phase, > results in a stable system. I can then load the module via kldload and > the system jumps then into X11-screen as usual. > > I recompile x11/nvidia-driver on a regular basis when recompiling the > kernel, so the module is always up to date and en par with the kernel > sources. > > The problem occurs idendependently of having kernel module drm.ko loaded > or not. I also tried falling back to the older nvidia driver 285.05.09 > (I use at the moment successfully 290.10). > > Before issuing a PR and doing a full debug reconfiguration of my box, > I'd like to ask whether this is a commong, well known problem since with > FreeBSD 9.0, I'd like to stay with STABLE rather than with RELEASE. No. But build your x11/nvidia-driver with no more than -O. Better with gcc (clang may be OK, but I'm not sure). Furthermore, if you use x11/nvidia-driver, you have no need to load drm.ko, which is for, e.g. radeon cards. > > Regards, > Oliver > > -- It is impossible for an optimist to be pleasantly surprised. ___ 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: How to detect the version of a installed perl module during portbuild
On 03/01/2012 23:41, Paul Schmehl wrote:
> This returns the installed package:
>
> pkg_info -qa | grep "p5-JSON-RPC" | sort | uniq
Woah! Try it like this:
pkg_info -Ex p5-JSON-RPC
> so maybe you could do something like?
>
> JSON_VER=`pkg_info -qa | grep "p5-JSON-RPC" | sort | uniq | cut -d'-' -f4`
JSON_VER=$( pkg_info -Ex p5-JSON-RPC | sed -e 's/^.*-//' )
> .if ${JSON_VER} >= 1
> do this
> .else
> do this
> .endif
case ${JSON_VER) in
1.*)
do_stuff
;;
0.*)
do_something_else
;;
esac
case does a string comparison using standard shell globbing rules --
it's a lot more flexible than trying to do maths on version numbers.
Using perl to generate the version number is also viable as suggested by
Jason:
perl -MJSON::RPC -le 'print $JSON::RPC::VERSION'
but it strikes me as slightly wasteful to fire up an entire perl
interpreter just to print out the value of one variable.
However, if the object is to create a port that has a BUILD_DEPENDS on
devel/p5-JSON-RPC then you only need to support what is already in the
ports -- and that's version 1.01. The BUILD_DEPENDS line can enforce that:
BUILD_DEPENDS = p5-JSON-RPC>=1.01:${PORTSDIR}/devel/p5-JSON-RPC
Should you have some program that requires JSON::RPC <= 0.96, then
create a p5-JSON-RPC-096 port to provide exactly that.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
best way to bind webserver to port 80 without running as root
Hi all, suddenly I'm facing this quest on freebsd 8. I need to bind my little webserver running aolserver to port 80. In the past I was always using port 8080 and had my router configured to forward requests on port 80 to the server on port 8080. However, I am planning to host my little site on a virtual server with a hosting company and figuredI can't use the workaround I always used. So my question is, how to bind aolserver to port 80 without running as root as I understood ports below 1024 can only be used by root. I found a sysctl net.inet.ip.portrange.reservedhigh which enables me to set it to 0. However, I don't know what the security ramifications are of using that. Are there any other options I could consider? Thanks Dino ___ 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-SA-11:07.chroot and ProFTPD 1.3.3g
Hi, My 7.4 is up to date and I have the latest proftpd But still it's not working :( What can I do? Any hint welcome. -- henk FreeBSD dee.signature.nl 7.4-STABLE FreeBSD 7.4-STABLE #1: Wed Jan 4 04:54:11 CET 2012 r...@bep.signature.nl:/usr/obj/usr/src/sys/BEP i386 BEP = GENERIC + IPFIREWALL_DEFAULT_TO_ACCEPT Jan 4 05:31:54 dee proftpd[22094]: 81.18.162.68 - ProFTPD 1.3.3g (maint) (built Wed Jan 4 2012 05:30:17 CET) standalone mode STARTUP Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - error: FreeBSD with vulnerable chroot (FreeBSD-SA-11:07.chroot) Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - chroot to '/home/henk' failed for user 'henk': Operation not permitted Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - error: unable to set default root directory ___ 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: best way to bind webserver to port 80 without running as root
On 01/04/2012 11:10 AM, Dino Vliet wrote: Hi all, suddenly I'm facing this quest on freebsd 8. I need to bind my little webserver running aolserver to port 80. In the past I was always using port 8080 and had my router configured to forward requests on port 80 to the server on port 8080. However, I am planning to host my little site on a virtual server with a hosting company and figuredI can't use the workaround I always used. So my question is, how to bind aolserver to port 80 without running as root as I understood ports below 1024 can only be used by root. I found a sysctl net.inet.ip.portrange.reservedhigh which enables me to set it to 0. However, I don't know what the security ramifications are of using that. Are there any other options I could consider? Thanks Dino ___ 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" http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mac-portacl.html ___ 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: How to detect the version of a installed perl module during portbuild
On 4 Jan 2012 08:59, "Matthew Seaman"
wrote:
>
> On 03/01/2012 23:41, Paul Schmehl wrote:
> > This returns the installed package:
> >
> > pkg_info -qa | grep "p5-JSON-RPC" | sort | uniq
>
> Woah! Try it like this:
>
> pkg_info -Ex p5-JSON-RPC
>
> > so maybe you could do something like?
> >
> > JSON_VER=`pkg_info -qa | grep "p5-JSON-RPC" | sort | uniq | cut -d'-'
-f4`
>
> JSON_VER=$( pkg_info -Ex p5-JSON-RPC | sed -e 's/^.*-//' )
$$(
It's a Makefile, don't forget ;)
>
> > .if ${JSON_VER} >= 1
> > do this
> > .else
> > do this
> > .endif
>
> case ${JSON_VER) in
>1.*)
>do_stuff
>;;
>0.*)
>do_something_else
>;;
> esac
>
> case does a string comparison using standard shell globbing rules --
> it's a lot more flexible than trying to do maths on version numbers.
>
> Using perl to generate the version number is also viable as suggested by
> Jason:
>
> perl -MJSON::RPC -le 'print $JSON::RPC::VERSION'
>
> but it strikes me as slightly wasteful to fire up an entire perl
> interpreter just to print out the value of one variable.
>
> However, if the object is to create a port that has a BUILD_DEPENDS on
> devel/p5-JSON-RPC then you only need to support what is already in the
> ports -- and that's version 1.01. The BUILD_DEPENDS line can enforce
that:
>
> BUILD_DEPENDS = p5-JSON-RPC>=1.01:${PORTSDIR}/devel/p5-JSON-RPC
>
> Should you have some program that requires JSON::RPC <= 0.96, then
> create a p5-JSON-RPC-096 port to provide exactly that.
>
>Cheers,
>
>Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
> Flat 3
> PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
> JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
>
___
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: FreeBSD-SA-11:07.chroot and ProFTPD 1.3.3g
On Wed, Jan 4, 2012 at 2:18 AM, Henk van Oers wrote: > > Hi, > > My 7.4 is up to date and I have the latest proftpd It's not. Have you done a 'make buildworld' and 'make installworld' after updating the source? If yes then try another cvsup server and report to the administrator. > But still it's not working :( > > What can I do? > Any hint welcome. > > -- henk > > FreeBSD dee.signature.nl 7.4-STABLE FreeBSD 7.4-STABLE #1: Wed Jan 4 > 04:54:11 CET 2012 r...@bep.signature.nl:/usr/obj/usr/src/sys/BEP i386 > > BEP = GENERIC + IPFIREWALL_DEFAULT_TO_ACCEPT > > Jan 4 05:31:54 dee proftpd[22094]: 81.18.162.68 - ProFTPD 1.3.3g (maint) > (built Wed Jan 4 2012 05:30:17 CET) standalone mode STARTUP > Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 > (81.18.162.68[81.18.162.68]) - error: FreeBSD with vulnerable chroot > (FreeBSD-SA-11:07.chroot) > Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 > (81.18.162.68[81.18.162.68]) - chroot to '/home/henk' failed for user > 'henk': Operation not permitted > Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 > (81.18.162.68[81.18.162.68]) - error: unable to set default root directory > > ___ > 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" -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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: best way to bind webserver to port 80 without running as root
On Wed 2012-01-04 (02:10), Dino Vliet wrote: > suddenly I'm facing this quest on freebsd 8. I need to bind my little > webserver running aolserver to port 80. In the past I was always using port > 8080 and had my router configured to forward requests on port 80 to the > server on port 8080. However, I am planning to host my little site on a > virtual server with a hosting company and figuredI can't use the workaround I > always used. So my question is, how to bind aolserver to port 80 without > running?as root as I understood ports below 1024 can only be used by root. > I found a sysctl net.inet.ip.portrange.reservedhigh which enables me to set > it to 0. However, I don't know what the security ramifications are of using > that. Are there any other options I could consider? Hi, if your server isn't able to bind as root and then drop its ownership then you can just run the process on a higher port number and use something like pf or portfwd to forward requests to port 80 to that higher port. ___ 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: How to detect the version of a installed perl module during portbuild
On 2012-01-03 21:52, Olli Hauer wrote:
> Hi,
>
> I'm searching a solution to detect the version of p5-JSON-RPC during build
> time.
>
> JSON-RPC-1.01 is *not* backward compatible to 0.96 so I have to apply a fix
> to the port only if JSON-RPC > 0.96 is installed.
>
>
>>From http://cpansearch.perl.org/src/DMAKI/JSON-RPC-1.01/Changes
> 1.00_01 2011 Nov 16
> - If you are using old JSON::RPC code (up to 0.96), DO NOT EXPECT
> YOUR CODE TO WORK. THIS VERSION IS BACKWARDS *INCOMPATIBLE*
> ...^^
>
Thanks for all the suggestions ;)
Meanwhile the following solutions was suggested from upstream (will be
implemented as patch in the port)
-use base qw(JSON::RPC::Server::CGI);
+BEGIN {
+eval { require JSON::RPC::Server::CGI; };
+if ($@) {
+require JSON::RPC::Legacy::Server::CGI;
+our @ISA = qw(JSON::RPC::Legacy::Server::CGI);
+}
+else {
+our @ISA = qw(JSON::RPC::Server::CGI);
+}
+}
--
olli
___
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: chinese/tin
** 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 Wed Jan 4 2012 12:00:29 UTC. - *chinese/tin* : zh-tin-2.0.1 < zh-tin-2.0.1_3 | revision 1.41 | date: 2012/01/02 15:34:21; author: leeym; state: Exp; lines: +2 -8 | - update to 2.0.1 | - drop maintainership | | PR:159863 | Submitted by: Yi-Rong Wang (master: news/tin) | revision 1.158 | date: 2011/12/29 08:21:56; author: johans; state: Exp; lines: +1 -1 | Update to tin 2.0.1 ___ 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"
linux-f10-nss_ldap: my first port - be gentle :)
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.include
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Cheers
___
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: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rock wrote:
> I've been advised I should attempt to port this for general use to
> FreeBSD. I've been operating it manually very successfully now in a
> number of operations. This is, however, my first attempt at a port and I
> would like some guidance to see if I've done this right.
>
> I was advised to copy the essential parts from a similar port, so I've
> used archivers/linux-f10-ucl. This is my Makefile:
>
> # New ports collection makefile for:archivers/linux-f10-nss_ldap
> # Date created:2012-01-04
> # Whom:rskinner
> #
> # $FreeBSD$
> #
>
> PORTNAME=nss_ldap
> PORTVERSION=1.03
> CATEGORIES=security linux
> MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
> PKGNAMEPREFIX=linux-f10-
> DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
>
> MAINTAINER=emulat...@freebsd.org
> COMMENT=nss_ldap library (Linux Fedora 10)
>
> CONFLICTS=
>
> USE_LINUX_RPM=yes
> LINUX_DIST_VER=10
> RPMVERSION=8.fc9
> USE_LDCONFIG=yes
>
> PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
> usr/lib/libnss_ldap-264.so
> DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
> PORTDOCS=COPYING NEWS README THANKS TODO
> DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
>
> .include
>
> And I have a pkg-descr file.
>
> Am I on the right track? I'm following the porters handbook as well.
>
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
--
Gary Jennejohn
___
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: redports.org - The public FreeBSD ports development infrastructure
On 02.01.2012 23:32, Doug Barton wrote: Is there such a thing as a redports mailing list? I neither have the infrastructure nor the time to setup and maintain my own list so I created one on Google Groups: redpo...@googlegroups.com https://groups.google.com/group/redports IRC was easy: #redports on Freenode irc://irc.freenode.net#redports -- Bernhard Froehlich http://www.bluelife.at/ ___ 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"
Porter's Handbook: PREFIX and DESTDIR
The section on PREFIX and DESTDIR in the Porter's Handbook is unclear and confusing. Following up from a thread in -doc, here are the proposed changes so far. Existing section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-prefix.html Proposed: http://www.wonkity.com/~wblock/porters-prefix/book.html#PORTING-PREFIX diff: http://www.wonkity.com/~wblock/porters-prefix/patch-porters-prefix.diff Beyond some rewriting and clarification, I removed the mention of LOCALBASE sometimes being /opt, which is covered by saying it can be a custom path. Is there any reason to keep the references to /usr/X11R6? Finally, this paragraph The variable PREFIX can be reassigned in your Makefile or in the user's environment. However, it is strongly discouraged for individual ports to set this variable explicitly in the Makefiles. is not clear, and was rewritten to PREFIX should not be set explicitly in a port's Makefile. Users installing the port may have set PREFIX to a custom location, and the port should respect that setting. Does that capture the intended meaning of the original? Has it left anything out? ___ 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: How to detect the version of a installed perl module during portbuild
--On January 4, 2012 8:59:12 AM + Matthew Seaman wrote: On 03/01/2012 23:41, Paul Schmehl wrote: This returns the installed package: pkg_info -qa | grep "p5-JSON-RPC" | sort | uniq Woah! Try it like this: pkg_info -Ex p5-JSON-RPC I bow to the master. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote: > On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock > wrote: > > > > I was advised to copy the essential parts from a similar port, so I've > > used archivers/linux-f10-ucl. This is my Makefile: [snip] > > Doesn't pass portlint. > > Can't fetch the RPM file. > > Otherwise, a pretty good start. It also lacks license information. -- 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: FreeBSD-SA-11:07.chroot and ProFTPD 1.3.3g
On Wed, 4 Jan 2012, Xin LI wrote: On Wed, Jan 4, 2012 at 2:18 AM, Henk van Oers wrote: My 7.4 is up to date and I have the latest proftpd It's not. Have you done a 'make buildworld' and 'make installworld' after updating the source? Yes, and 'ezjail-admin update -i' to 'installworld' in the jales and 'ezjail-admin update -P' for the proftpd port in the jail. If yes then try another cvsup server and report to the administrator. diff stable-supfile~ stable-supfile 68c68 < *default host=cvsup.nl.FreeBSD.org --- *default host=cvsup.de.FreeBSD.org But still it's not working :( What can I do? Any hint welcome. -- henk FreeBSD dee.signature.nl 7.4-STABLE FreeBSD 7.4-STABLE #1: Wed Jan 4 04:54:11 CET 2012 r...@bep.signature.nl:/usr/obj/usr/src/sys/BEP i386 BEP = GENERIC + IPFIREWALL_DEFAULT_TO_ACCEPT Jan 4 05:31:54 dee proftpd[22094]: 81.18.162.68 - ProFTPD 1.3.3g (maint) (built Wed Jan 4 2012 05:30:17 CET) standalone mode STARTUP Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - error: FreeBSD with vulnerable chroot (FreeBSD-SA-11:07.chroot) Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - chroot to '/home/henk' failed for user 'henk': Operation not permitted Jan 4 05:32:21 dee proftpd[22131]: 81.18.162.68 (81.18.162.68[81.18.162.68]) - error: unable to set default root directory ___ 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" -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die ___ 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: redports.org - The public FreeBSD ports development infrastructure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/4/12 3:07 AM, Bernhard Froehlich wrote: > On 03.01.2012 22:32, Greg Larkin wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 12/29/11 6:44 AM, Bernhard Froehlich wrote: >>> Hi Porters! >>> >>> I am happy to announce that redports.org has finally >>> reached the point where I think It's safe to be used >>> by everybody! In case you never heard of it before >>> redports is the result of an idea born at EuroBSDCon >>> 2011 in Karlsruhe to give Port Maintainers and Port >>> Committers a public service to test their new ports >>> or ports patches during development or before >>> submitting a ports PR. >>> >> [...] >> >> Wow! Stellar job, Bernhard, and I'm looking forward to using >> redports.org for fixing ports that are broken under clang. > > Hope you don't want to do that today because during the night the > current building machine paniced and needs someone power cycling > it. I will do this in the evening so no builds today :( > > It looks like I could get some hardware from portmgr so > hopefully more hardware and redundancy is available soon. > >> I noticed one minor typo on https://redports.org/buildgroups: >> automaticaly -> automatically > > Thanks, it's fixed now! > Hi again Bernhard, It looks like ports are building fine now. As I was building the first port on your system, I thought of an enhancement, and I am interested to know how difficult it would be to implement. I maintain various p5- and py- ports, and I often want to test them under multiple versions of Perl and Python, in case there are conditional behaviors in the Makefile. Assuming you're not planning on allowing users to create their own builds, what about adding the ability to set build variables in a make.conf file? For instance, if I commit etc/make.conf to my personal repository location, redports would overlay my options before starting the build. Then I could do things like force Python version 2.7, Perl version 5.10, etc. What do you think? Thank you, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8EmIsACgkQ0sRouByUApAegQCgxgLcmbZihiQUtUj2TzYXPhrY xncAoLZ19vyGQP1bPnaNdfbNa6Gm6Bcg =Bus6 -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: redports.org - The public FreeBSD ports development infrastructure
On 04.01.2012 19:21, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 1/4/12 3:07 AM, Bernhard Froehlich wrote: On 03.01.2012 22:32, Greg Larkin wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/29/11 6:44 AM, Bernhard Froehlich wrote: Hi Porters! I am happy to announce that redports.org has finally reached the point where I think It's safe to be used by everybody! In case you never heard of it before redports is the result of an idea born at EuroBSDCon 2011 in Karlsruhe to give Port Maintainers and Port Committers a public service to test their new ports or ports patches during development or before submitting a ports PR. [...] Wow! Stellar job, Bernhard, and I'm looking forward to using redports.org for fixing ports that are broken under clang. Hope you don't want to do that today because during the night the current building machine paniced and needs someone power cycling it. I will do this in the evening so no builds today :( It looks like I could get some hardware from portmgr so hopefully more hardware and redundancy is available soon. I noticed one minor typo on https://redports.org/buildgroups: automaticaly -> automatically Thanks, it's fixed now! Hi again Bernhard, It looks like ports are building fine now. As I was building the first port on your system, I thought of an enhancement, and I am interested to know how difficult it would be to implement. I maintain various p5- and py- ports, and I often want to test them under multiple versions of Perl and Python, in case there are conditional behaviors in the Makefile. Assuming you're not planning on allowing users to create their own builds, what about adding the ability to set build variables in a make.conf file? For instance, if I commit etc/make.conf to my personal repository location, redports would overlay my options before starting the build. Then I could do things like force Python version 2.7, Perl version 5.10, etc. What do you think? That sounds a lot like OPTIONS support. Tinderbox is already able to do that so the only thing I need to solve are that it has to work in a shared environment. That means it will have to build all dependencies from scratch all the time because there are too many combinations and we don't really support mixing and matching weird combinations of slave ports (though everybody does it). Then add some user interface to enter contents of make.conf. OPTIONS support is already on my todo since the very beginning but I have no idea on when I will be able to work on that. -- Bernhard Froehlich http://www.bluelife.at/ ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
wrote:
> I've been advised I should attempt to port this for general use to
> FreeBSD. I've been operating it manually very successfully now in a
> number of operations. This is, however, my first attempt at a port
> and I would like some guidance to see if I've done this right.
>
> I was advised to copy the essential parts from a similar port, so
> I've used archivers/linux-f10-ucl. This is my Makefile:
>
> # New ports collection makefile for:archivers/linux-f10-nss_ldap
> # Date created:2012-01-04
> # Whom:rskinner
> #
> # $FreeBSD$
> #
>
> PORTNAME=nss_ldap
> PORTVERSION=1.03
> CATEGORIES=security linux
> MASTER_SITES= CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
> PKGNAMEPREFIX=linux-f10-
> DISTNAME= ${PORTNAME}-${PORTVERSION}-${RPMVERSION}
>
> MAINTAINER=emulat...@freebsd.org
This should be you (if you're willing to maintain the port).
> COMMENT=nss_ldap library (Linux Fedora 10)
>
> CONFLICTS=
>
> USE_LINUX_RPM=yes
> LINUX_DIST_VER=10
> RPMVERSION=8.fc9
This does not sound like you took a Fedora 10 RPM here, but you
specified in LINUX_DIST_VER that you use Fedora 10.
> USE_LDCONFIG=yes
>
> PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
> usr/lib/libnss_ldap-264.so
> DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
> PORTDOCS=COPYING NEWS README THANKS TODO
> DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
You don't need DESCR this way, it looks like this sets it to the same
file (but in a different way) than the default value of DESCR.
> .include
>
> And I have a pkg-descr file.
>
> Am I on the right track? I'm following the porters handbook as well.
When doing the "make makesum", please use "make -DPACKAGE_BUILDING
makesum" to get the checkums of the SRPMs recorded too. We are obliged
to provide the GNU sources the same way like the binaries, and IIRC we
have some logic which fetches the SRPMs on tha packaga bulding cluster.
Bye,
Alexander.
--
http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
___
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: Porter's Handbook: PREFIX and DESTDIR
On Wed, Jan 4, 2012 at 9:22 AM, Warren Block wrote: > The section on PREFIX and DESTDIR in the Porter's Handbook is unclear and > confusing. Following up from a thread in -doc, here are the proposed > changes so far. Thanks for working on this. > Beyond some rewriting and clarification, I removed the mention of LOCALBASE > sometimes being /opt, which is covered by saying it can be a custom path. It may be useful to give an explicit example of what paths users choose. > Is there any reason to keep the references to /usr/X11R6? No, all references to X11BASE will be removed shortly anyways. > is not clear, and was rewritten to > > PREFIX should not be set explicitly in a port's Makefile. Users > installing the port may have set PREFIX to a custom location, and the > port should respect that setting. > > Does that capture the intended meaning of the original? Has it left > anything out? This is much better. -- Eitan Adler ___ 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: redports.org - The public FreeBSD ports development infrastructure
On 01/04/2012 06:00, Bernhard Froehlich wrote: > On 02.01.2012 23:32, Doug Barton wrote: >> Is there such a thing as a redports mailing list? > > I neither have the infrastructure nor the time to > setup and maintain my own list so I created one on > Google Groups: > > redpo...@googlegroups.com > https://groups.google.com/group/redports > > IRC was easy: > #redports on Freenode > irc://irc.freenode.net#redports That's awesome! Perhaps now the discussion about redports can start migrating to that group? Doug -- You can observe a lot just by watching. -- Yogi Berra 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/04/12 23:27, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000
Da Rock wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port and I
would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES=CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME=${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
.include
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
Ok, thats good so far then. Thanks for the assessment.
Now, what's portlint?
And I have a question or two about the rpm. Do I need to script
something to just extract the files needed, or is it already in the mk
files already somewhere?
And how do I work out the url for fetching the rpm? This particular one
is a moving target as the distro is already eol. Is it stored on the
FreeBSD servers? Or what do I do here?
In the porters handbook it mentions checksums and "make makesum" - does
that mean I have to put it in the ports tree to try it?
And is pkg-message scripted or do I just create it?
Thanks again.
___
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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 01:41, Chad Perrin wrote: On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote: On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock wrote: I was advised to copy the essential parts from a similar port, so I've used archivers/linux-f10-ucl. This is my Makefile: [snip] Doesn't pass portlint. Can't fetch the RPM file. Otherwise, a pretty good start. It also lacks license information. How do I set that? Its linux so its GPL. ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 07:10, Alexander Leidinger wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
wrote:
I've been advised I should attempt to port this for general use to
FreeBSD. I've been operating it manually very successfully now in a
number of operations. This is, however, my first attempt at a port
and I would like some guidance to see if I've done this right.
I was advised to copy the essential parts from a similar port, so
I've used archivers/linux-f10-ucl. This is my Makefile:
# New ports collection makefile for:archivers/linux-f10-nss_ldap
# Date created:2012-01-04
# Whom:rskinner
#
# $FreeBSD$
#
PORTNAME=nss_ldap
PORTVERSION=1.03
CATEGORIES=security linux
MASTER_SITES= CRITICAL/rpm/${LINUX_RPM_ARCH}/fedora/${LINUX_DIST_VER}
PKGNAMEPREFIX=linux-f10-
DISTNAME= ${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER=emulat...@freebsd.org
This should be you (if you're willing to maintain the port).
You keep dropping hints like this all the time Alex :)
Honestly, though, I'm not sure whats involved or whether I'm capable of
handling the responsibility. This one is not likely to change too much
over time, but my skills are probably wanting.
COMMENT=nss_ldap library (Linux Fedora 10)
CONFLICTS=
USE_LINUX_RPM=yes
LINUX_DIST_VER=10
RPMVERSION=8.fc9
This does not sound like you took a Fedora 10 RPM here, but you
specified in LINUX_DIST_VER that you use Fedora 10.
I wasn't sure exactly what to put there yet, but this was a Makefile for
linux-f10-ucl so I thought it would be at least close. The filename is
supposed to be nss_ldap-264-6.fc10.i386.rpm.
USE_LDCONFIG=yes
PLIST_FILES=usr/lib/libnss_ldap.so.2 usr/lib/libnss_ldap.so
usr/lib/libnss_ldap-264.so
DOCSDIR=${PREFIX}/usr/share/doc/${PORTNAME}-${PORTVERSION}
PORTDOCS=COPYING NEWS README THANKS TODO
DESCR=${.CURDIR}/../${PORTNAME}/pkg-descr
You don't need DESCR this way, it looks like this sets it to the same
file (but in a different way) than the default value of DESCR.
I have a pkg-descr file setup. That should be right, isn't it?
.include
And I have a pkg-descr file.
Am I on the right track? I'm following the porters handbook as well.
When doing the "make makesum", please use "make -DPACKAGE_BUILDING
makesum" to get the checkums of the SRPMs recorded too. We are obliged
to provide the GNU sources the same way like the binaries, and IIRC we
have some logic which fetches the SRPMs on tha packaga bulding cluster.
Oh, dear. I'll have to go hunting for them then.
___
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: FreeBSD-SA-11:07.chroot and ProFTPD 1.3.3g
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On 01/04/12 10:10, Henk van Oers wrote: > > On Wed, 4 Jan 2012, Xin LI wrote: >> On Wed, Jan 4, 2012 at 2:18 AM, Henk van Oers >> wrote: >>> >>> My 7.4 is up to date and I have the latest proftpd >> >> It's not. Have you done a 'make buildworld' and 'make >> installworld' after updating the source? > > Yes, and 'ezjail-admin update -i' to 'installworld' in the jales > and 'ezjail-admin update -P' for the proftpd port in the jail. > >> If yes then try another cvsup server and report to the >> administrator. > > diff stable-supfile~ stable-supfile 68c68 < *default > host=cvsup.nl.FreeBSD.org --- >> *default host=cvsup.de.FreeBSD.org > > > But still it's not working :( Could you please do: grep __FreeBSD_libc_enter_restricted_mode /usr/lib/libc.so And see if the output would be: Binary file /usr/lib/libc.so matches ? Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8E/EsACgkQOfuToMruuMAE/gCfR9xV0yPKP3SF/7FuYChzf+ut rT0An0O82shFe+/dDLCxlVjcKy7dBR6f =i0lk -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: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 09:53:25AM +1000, Da Rock wrote:
> On 01/05/12 01:41, Chad Perrin wrote:
> >On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote:
> >>On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
> >> wrote:
> >>>I was advised to copy the essential parts from a similar port, so I've
> >>>used archivers/linux-f10-ucl. This is my Makefile:
> >[snip]
> >
> >>Doesn't pass portlint.
> >>
> >>Can't fetch the RPM file.
> >>
> >>Otherwise, a pretty good start.
> >It also lacks license information.
> >
> How do I set that? Its linux so its GPL.
This is an example from /usr/ports/x11/xsel-conrad/Makefile:
LICENSE=xsel-conrad
LICENSE_GROUPS= COPYFREE
LICENSE_NAME= xsel-conrad license
LICENSE_FILE= ${WRKSRC}/COPYING
LICENSE_PERMS= auto-accept dist-mirror dist-sell pkg-mirror pkg-sell
I'm not sure it's perfect port maintainer Makefile practice, but it
works, and it's a lot better than no license information at all in my
opinion. I'd suggest checking that Makefile to see where in the Makefile
to put it.
. . . and if anyone who is more knowledgeable about this stuff than I am
sees something wrong with that Makefile, please let me know.
--
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: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 10:42:17AM +1000, Da Rock wrote: > On 01/05/12 07:10, Alexander Leidinger wrote: > > > >This should be you (if you're willing to maintain the port). > > You keep dropping hints like this all the time Alex :) > > Honestly, though, I'm not sure whats involved or whether I'm capable > of handling the responsibility. This one is not likely to change too > much over time, but my skills are probably wanting. The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). -- 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: Porter's Handbook: PREFIX and DESTDIR
On Wed, 4 Jan 2012, Eitan Adler wrote: Beyond some rewriting and clarification, I removed the mention of LOCALBASE sometimes being /opt, which is covered by saying it can be a custom path. It may be useful to give an explicit example of what paths users choose. Done, but not in a way that admits the original might have had a point. Is there any reason to keep the references to /usr/X11R6? No, all references to X11BASE will be removed shortly anyways. Okay, ripped that out and edited that section a little. New version in the same place. Existing section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-prefix.html Proposed: http://www.wonkity.com/~wblock/porters-prefix/book.html#PORTING-PREFIX diff: http://www.wonkity.com/~wblock/porters-prefix/patch-porters-prefix.diff ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:11, Chad Perrin wrote: On Thu, Jan 05, 2012 at 10:42:17AM +1000, Da Rock wrote: On 01/05/12 07:10, Alexander Leidinger wrote: This should be you (if you're willing to maintain the port). You keep dropping hints like this all the time Alex :) Honestly, though, I'm not sure whats involved or whether I'm capable of handling the responsibility. This one is not likely to change too much over time, but my skills are probably wanting. The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 12:08, Chad Perrin wrote:
On Thu, Jan 05, 2012 at 09:53:25AM +1000, Da Rock wrote:
On 01/05/12 01:41, Chad Perrin wrote:
On Wed, Jan 04, 2012 at 02:27:57PM +0100, Gary Jennejohn wrote:
On Wed, 04 Jan 2012 22:31:51 +1000 Da Rock
wrote:
I was advised to copy the essential parts from a similar port, so I've
used archivers/linux-f10-ucl. This is my Makefile:
[snip]
Doesn't pass portlint.
Can't fetch the RPM file.
Otherwise, a pretty good start.
It also lacks license information.
How do I set that? Its linux so its GPL.
This is an example from /usr/ports/x11/xsel-conrad/Makefile:
LICENSE=xsel-conrad
LICENSE_GROUPS= COPYFREE
LICENSE_NAME= xsel-conrad license
LICENSE_FILE= ${WRKSRC}/COPYING
LICENSE_PERMS= auto-accept dist-mirror dist-sell pkg-mirror pkg-sell
I'm not sure it's perfect port maintainer Makefile practice, but it
works, and it's a lot better than no license information at all in my
opinion. I'd suggest checking that Makefile to see where in the Makefile
to put it.
Ok. I've been working through the handbook step by step, and I'm stuck
at checksums so I probably haven't yet reached that part yet. I'll check
it out now
___
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: Porter's Handbook: PREFIX and DESTDIR
New version in the same place. Existing section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-prefix.html Proposed: http://www.wonkity.com/~wblock/porters-prefix/book.html#PORTING-PREFIX diff: http://www.wonkity.com/~wblock/porters-prefix/patch-porters-prefix.diff Now that most of this section has been bludgeoned into relative submission, returning to this issue mentioned by Benjamin Kaduk in -doc: quote from the proposed new version: The value of PREFIX will be set to LOCALBASE (defaulting to /usr/local). If USE_LINUX_PREFIX is set, PREFIX will be LINUXBASE (defaulting to /compat/linux). Quoth Benjamin Kaduk: I don't think we've yet said something like: LOCALBASE should be set to where existing ports have already been installed (the ``base directory'' of where the ``local additions'' to the system have been made); it is uncommon for having PREFIX != LOCALBASE in normal usage. We probably should say something like that. Thinking about this a bit, it seems like something to tell the end user rather than the porter. Although maybe it is something the porter should consider. I don't know. ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: > On 01/05/12 12:11, Chad Perrin wrote: > > > >The best way to learn, I think, is to get yourself a mentor and jump in. > >That's how I'm doing it (and yeah, that means I'm not the right person to > >mentor you). > > Thats what I'm looking for, alright. I've been looking for a few > years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? -- 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: linux-f10-nss_ldap: my first port - be gentle :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: > On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: >> On 01/05/12 12:11, Chad Perrin wrote: >>> >>> The best way to learn, I think, is to get yourself a mentor and jump in. >>> That's how I'm doing it (and yeah, that means I'm not the right person to >>> mentor you). >> >> Thats what I'm looking for, alright. I've been looking for a few >> years now. Any suggestions? > > Ask on this list, I guess. > > Hey -- does anyone (qualified) want to mentor Da Rock as a port > maintainer? > As much as I hate to toss Chris Rees "under the bus" on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a "mentor", I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Other than that, I can always help out as much as I can with questions if you want to email me directly about your port. I know the ins-and-outs about porting and I'd be more than happy to lend a hand. Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8FI1MACgkQGK3MsUbJZn6WcwCeNZykh5WFpdVHhrlpmyqDd1Qn Hb0AnjDVIKpx/9BCiQt9U2pPh6QV9oKs =2XFi -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: linux-f10-nss_ldap: my first port - be gentle :)
On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jay wrote: > As much as I hate to toss Chris Rees "under the bus" on this, he's > be EXTREMELY helpful to me when creating ports that have small hiccups > like this. He's very knowledgeable. While he might be a bit too busy to > be a "mentor", I'm sure he wouldn't have a problem pointing you in the > right direction(s) if you have questions about ports. He'll most likely > reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. -- Eitan Adler ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:13, Janketh Jay wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys! On 01/04/2012 08:19 PM, Chad Perrin wrote: On Thu, Jan 05, 2012 at 12:20:45PM +1000, Da Rock wrote: On 01/05/12 12:11, Chad Perrin wrote: The best way to learn, I think, is to get yourself a mentor and jump in. That's how I'm doing it (and yeah, that means I'm not the right person to mentor you). Thats what I'm looking for, alright. I've been looking for a few years now. Any suggestions? Ask on this list, I guess. Hey -- does anyone (qualified) want to mentor Da Rock as a port maintainer? As much as I hate to toss Chris Rees "under the bus" on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a "mentor", I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Other than that, I can always help out as much as I can with questions if you want to email me directly about your port. I know the ins-and-outs about porting and I'd be more than happy to lend a hand. Regards, Janky Jay, III Thanks Jay. ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
On 01/05/12 14:15, Eitan Adler wrote: On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jay wrote: As much as I hate to toss Chris Rees "under the bus" on this, he's be EXTREMELY helpful to me when creating ports that have small hiccups like this. He's very knowledgeable. While he might be a bit too busy to be a "mentor", I'm sure he wouldn't have a problem pointing you in the right direction(s) if you have questions about ports. He'll most likely reply to this with what he thinks about it... Or just continue to ask on this mailing list. No need to bug specific people when you could get everyone to answer you. You could also pop by on #bsdports on EFNet. A lot of us hang out there. Oh you can be sure I'll be doing that :) I'm only just starting IRC (if thats what you mean there), but I'll drop in once I'm configured. ___ 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: linux-f10-nss_ldap: my first port - be gentle :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Rock, On 01/04/2012 09:24 PM, Da Rock wrote: > On 01/05/12 14:15, Eitan Adler wrote: >> On Wed, Jan 4, 2012 at 11:13 PM, Janketh Jay wrote: >>> As much as I hate to toss Chris Rees "under the bus" on this, he's >>> be EXTREMELY helpful to me when creating ports that have small hiccups >>> like this. He's very knowledgeable. While he might be a bit too busy to >>> be a "mentor", I'm sure he wouldn't have a problem pointing you in the >>> right direction(s) if you have questions about ports. He'll most likely >>> reply to this with what he thinks about it... >> Or just continue to ask on this mailing list. No need to bug specific >> people when you could get everyone to answer you. >> You could also pop by on #bsdports on EFNet. A lot of us hang out there. > Oh you can be sure I'll be doing that :) > > I'm only just starting IRC (if thats what you mean there), but I'll drop in once I'm configured. Yup. IRC is correct. EFNet is pretty helpful in the right channels (I would advise staying away from the dingleberries in the "I art better than thou" channels. :) .) You'll certainly get help in #bsdports, though. Also, might I recommend Irssi as an IRC client. \o/ Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8FKY0ACgkQGK3MsUbJZn4iXgCfRl+oaGJKXp2NFDWe8GPJoo84 cbcAn2C6BMtBjvwf8kFcwlGr9GfmA1l2 =9Ss8 -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: VirtualBox, vboxwebsrv and VRDPAuth
Em Ter, 2012-01-03 às 09:19 +0100, Bernhard Froehlich escreveu: > On 02.01.2012 22:23, Marek Salwerowicz wrote: > > Hi all, > > > > My host is 9.0-RC3 amd64. > > > > I've installed VirtualBox from /usr/ports/emulation/virtualbox-ose > > port, with GUESTADDITIONS, DBUS, VNC and WEBSERVICE options. > > I use FBSD amd64, without VRDP and virtualbox 4.1.8 from redports, and started it with VNC, installed a windows XP (32) and runs like a charm.. I configured windows to remote administration (rdp) and can than access all of the VM funcions without problem Sergio ___ 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"
