Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill annoying port email Fenner ___ 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
Help making a port for a (somewhat) restricted program
I'm creating a port for Petite Chez Scheme [1], which is a free interpreter
for commercial Chez Scheme, and has some licensing restrictions.
From what I understood in the license [2], user must accept it before
installing.
The text of the license is also distributed in the tarball, so it
seems appropriate
to simply display the license file on post-extract.
Is there a common way to display such a file before installing?
I'm currently using ${PAGER} for that [3], but it's unlike any other
port we have.
There's also a problem with packages: you can't create one unless
there's a way to show the license on pkg_add. I believe that pkg-install script
can be used here, but I don't think that putting the whole license inside
hat script is a good idea.
Currently I've forbidden making packages; any thoughts on the right way
to do that?
And the last issue: depending on a command line switch the port
requires fetching two different files. The way I've set it up is to set
a parameter depending on the switch, and then use it in DISTNAME.
In short, that makes portlint go crazy. Help on this is also appreciated.
[1] http://scheme.com/petitechezscheme.html
[2] http://scheme.com/download/petite-lic.html
[3] http://tx97/pub/patches/petite-chez.shar
___
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
Help making a port for a (somewhat) restricted program
Vitaly Magerya writes:
I'm creating a port for Petite Chez Scheme [1], which is a free
interpreter for commercial Chez Scheme, and has some licensing
restrictions.
From what I understood in the license [2], user must accept it
before installing. The text of the license is also distributed
in the tarball, so it seems appropriate to simply display the
license file on post-extract.
Is there a common way to display such a file before installing?
I'm currently using ${PAGER} for that [3], but it's unlike any other
port we have.
Look at how java/jdk-* does it.
Robert Huff
___
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: Help making a port for a (somewhat) restricted program
Look at how java/jdk-* does it.
java/jdk* uses ${PRINTF} (/usr/bin/printf) to display a message about
you having to go and download some of the restricted files, and then exits.
Once you've downloaded the files (and that implies that you've accepted
the license), the message no longer appears, and you can proceed with
installation.
(This seems to be the common way of treating restricted ports).
The difference with Petite Chez is that you do not need to accept anything
to download sources (no restriction on redistribution), so this part can be
automated; but you do have to read and accept the license before
installing it. ${PRINTF} won't help too much, as you can't display a
file with it;
and license is too big to fit on one screen anyway (that's why I'd use a pager).
___
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: Help making a port for a (somewhat) restricted program
Vitaly Magerya writes:
Look at how java/jdk-* does it.
java/jdk* uses ${PRINTF} (/usr/bin/printf) to display a message about
you having to go and download some of the restricted files, and then exits.
Once you've downloaded the files (and that implies that you've accepted
the license), the message no longer appears, and you can proceed with
installation.
(This seems to be the common way of treating restricted ports).
I just re-compiled jdk-1.6 (all 6 hours of it) yesterday.
After unpacking the tarball(s) but before config. it popped up the
Sun license and asked for a yes/no. I have no idea exactly how.
Robert Huff
___
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: Help making a port for a (somewhat) restricted program
I just re-compiled jdk-1.6 (all 6 hours of it) yesterday. After unpacking the tarball(s) but before config. it popped up the Sun license and asked for a yes/no. I have no idea exactly how. Oh, yes, I missed that part somehow. The port has a script in it that shows the license and asks for yes/no. Looks good; I think I'll do that too. Thanks! (The first time I've mistakenly sent this only to Robert). ___ 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: Help making a port for a (somewhat) restricted program
[3] http://tx97/pub/patches/petite-chez.shar That should have been http://tx97.net/pub/patches/petite-chez.shar ___ 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
Installing in cgi-bin
I have a Perl program that I am thinking of porting to FreeBSD. The
program has to be installed in the 'cgi-bin'.
I was thinking something like:
$(WWWDIR}/apache${APACHE_VERSION}/cgi-bin might be the way to direct
the install to the correct directory. Is there a better way? I cannot
find a macro that directly references the cgi-bin.
--
Jerry
ges...@yahoo.com
Adde parvum parvo manus acervus erit.
[Add little to little and there will be a big pile.]
Ovid
signature.asc
Description: PGP signature
Re: Installing in cgi-bin
On Sat, Mar 28, 2009 at 01:33:15PM -0400, Jerry wrote:
I have a Perl program that I am thinking of porting to FreeBSD. The
program has to be installed in the 'cgi-bin'.
I was thinking something like:
$(WWWDIR}/apache${APACHE_VERSION}/cgi-bin might be the way to direct
the install to the correct directory. Is there a better way? I cannot
find a macro that directly references the cgi-bin.
We have a policy against installations that would automaticlly be on
the network. You need to install it elsewhere (often a directory
under WWWDIR) and tell people how to add the appropriate configuration
directives to http.conf or to copy the file into cgi-bin in pkg-message.
-- Brooks
pgpFPUHdW2yCL.pgp
Description: PGP signature
Re: is anyone working on a openjdk port
On Sat, Mar 28, 2009 at 12:41 AM, Peter Ulrich Kruppa ulr...@pukruppa.netwrote: matt donovan schrieb: I been thinking about making it but if someone already started I won't I just not had the time at the moment to start it since it'll be good to have in the port tree even if it needs a java installed to bootstrap it There already is a java/openjdk6 port in the tree and there was some email traffic about openjdk7 . Greetings Uli. ___ 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 ah ok just have not seen anything about openjdk port since I was thinking about writing a port for some applications but I can write openjdk off my list 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
LATEST_LINK not in index
I'm working on a binary package upgrade tool that gets all required information from the INDEX file downloadable from the package repositories. This means you do not need a local copy of the ports tree to use it. The only information required and missing is the LATEST_LINK. Normally this is easily done by stripping the package name of the version, but some ports define a proprietary LATEST_LINK to avoid conflicts. This leads to the following problem, my program has to do some guessing and in these cases it fails: # pkg_upgrade firefox3 # # pkg_upgrade firefox www/firefox;firefox-2.0.0.20_4,1 www/firefox3;firefox-3.0.7,1 # It either matches none or more than one port. I could build some guessing logic, but the real solution would be to have the LATEST_LINK name in the index file. Is there any chance a LATEST_LINK column will be added if I file a PR? ___ 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: Installing in cgi-bin
On Sat, 28 Mar 2009 12:43:13 -0500
Brooks Davis bro...@freebsd.org wrote:
On Sat, Mar 28, 2009 at 01:33:15PM -0400, Jerry wrote:
I have a Perl program that I am thinking of porting to FreeBSD. The
program has to be installed in the 'cgi-bin'.
I was thinking something like:
$(WWWDIR}/apache${APACHE_VERSION}/cgi-bin might be the way to
direct the install to the correct directory. Is there a better way?
I cannot find a macro that directly references the cgi-bin.
We have a policy against installations that would automaticlly be on
the network. You need to install it elsewhere (often a directory
under WWWDIR) and tell people how to add the appropriate configuration
directives to http.conf or to copy the file into cgi-bin in
pkg-message.
The program is DADA Mail. It installs a 'mail.cgi' in the cgi-bin and
then installs the rest of its files, perl modules, etc. in a hierarchy
several layers deep in the cgi-bin directory. We are talking
about a lot of files here. Expecting the end user to properly move the
files from a temporary directory to the cgi-bin and then properly
changing the file(s) properties would seem a little extreme. However,
if that is the only way I can do it, I will investigate writing a
script that the end user could invoke to accomplish this feat. It does
seem a little over the top however. Due to the way DADA Mail is
written, the author does not believe it can be run from other than that
directory along with its associated files.
--
Jerry
ges...@yahoo.com
If you think education is expensive, try ignorance.
Derek Bok, president of Harvard
signature.asc
Description: PGP signature
FreeBSD Port: sysutils/webmin perl 5.8.9
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After upgrading perl to 5.8.0 because of a vuln, I found webmin would not start. $ tail /var/log/webmin/miniserv.error /libexec/ld-elf.so.1: /usr/local/lib/perl5/5.8.9/mach/auto/SDBM_File/SDBM_File.so: Undefined symbol sdbm_open FWIW, perl-after-upgrade has been run. We have: webmin-1.470_1 perl-5.8.9_2 uname -a FreeBSD batteries.example.com 7.0-STABLE FreeBSD 7.0-STABLE #0: Sun Jul 13 10:38:38 CDT 2008 ad...@example.local:/usr/obj/usr/src/sys/BWD amd64 - -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknOgEUACgkQCgsXFM/7nTwrVgCfcxmjtxbFTcLbst3lJ8si2GrU b0QAni25unaubjrXMQRr6tvPr7g0p36D =Kg1a -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: Installing in cgi-bin
On Sat, Mar 28, 2009 at 04:07:30PM -0400, Jerry wrote:
On Sat, 28 Mar 2009 12:43:13 -0500
Brooks Davis bro...@freebsd.org wrote:
On Sat, Mar 28, 2009 at 01:33:15PM -0400, Jerry wrote:
I have a Perl program that I am thinking of porting to FreeBSD. The
program has to be installed in the 'cgi-bin'.
I was thinking something like:
$(WWWDIR}/apache${APACHE_VERSION}/cgi-bin might be the way to
direct the install to the correct directory. Is there a better way?
I cannot find a macro that directly references the cgi-bin.
We have a policy against installations that would automaticlly be on
the network. You need to install it elsewhere (often a directory
under WWWDIR) and tell people how to add the appropriate configuration
directives to http.conf or to copy the file into cgi-bin in
pkg-message.
The program is DADA Mail. It installs a 'mail.cgi' in the cgi-bin and
then installs the rest of its files, perl modules, etc. in a hierarchy
several layers deep in the cgi-bin directory. We are talking
about a lot of files here. Expecting the end user to properly move the
files from a temporary directory to the cgi-bin and then properly
changing the file(s) properties would seem a little extreme. However,
if that is the only way I can do it, I will investigate writing a
script that the end user could invoke to accomplish this feat. It does
seem a little over the top however. Due to the way DADA Mail is
written, the author does not believe it can be run from other than that
directory along with its associated files.
Sounds seriously broken. :) I might suggest installing in www/dada and
providing a script to make appropriate symlinks along with an instruction
to enable following symlinks in cgi-bin. It seems like shockingly bad
design to require that it live at http://.../cgi-bin/mail.cgi, but
that's certainly not uncommon. :(
-- Brooks
pgpOn77FZYYNc.pgp
Description: PGP signature
Re: REQUEST FOR TESTERS: `devel/mingw32-gcc'
Coleman Kane wrote: Lev Serebryakov wrote: Hello ports, Latest versions of `mingw32-binutils' and `mingw32-bin-msvcrt' were committed. `mingw32-gcc' is on pipeline. But it is BIG update: new version is 4.2.0 I ask you to test this `almost new' port before commit. http://lev.serebryakov.spb.ru/download/port-mingw32-gcc-4.2.0.tar.gz Many thanks to Coleman Kane cok...@freebsd.org, who helps me to prepare this update. I'd like to know what everyone else's experience with these new mingw32- ports are. So far I have been building Win32 applications from my FreeBSD box with these versions quite successfully. I think that the binutils and GCC are actually newer than the ones currently shipping with the MinGW32 binary distribution too. -- Coleman Kane I haven't seen any activity on the above email, and I am curious if: 1) It was missed (and this really does affect people) 2) Nobody cross-compiles using the mingw32-* ports (it is really very handy!) 3) Nobody really cares that mingw32-gcc will move from 3.4.5 -- 4.2.0 Please, if this affects you test out the above port tarball! Otherwise, this will end up going in and not take into account any problems that might arise in your environment. -- Coleman Kane ___ freebsd-hack...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@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: REQUEST FOR TESTERS: `devel/mingw32-gcc'
Coleman Kane wrote: I haven't seen any activity on the above email, and I am curious if: 1) It was missed (and this really does affect people) 2) Nobody cross-compiles using the mingw32-* ports (it is really very handy!) 3) Nobody really cares that mingw32-gcc will move from 3.4.5 -- 4.2.0 Please, if this affects you test out the above port tarball! Otherwise, this will end up going in and not take into account any problems that might arise in your environment. -- Coleman Kane I just saw that this message is about two years old, and that the commit must have been made years ago. Sorry for the noise. ___ 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: REQUEST FOR TESTERS: `devel/mingw32-gcc'
Coleman Kane wrote: http://lev.serebryakov.spb.ru/download/port-mingw32-gcc-4.2.0.tar.gz I haven't seen any activity on the above email, and I am curious if: 1) It was missed (and this really does affect people) 2) Nobody cross-compiles using the mingw32-* ports (it is really very handy!) 3) Nobody really cares that mingw32-gcc will move from 3.4.5 -- 4.2.0 Please, if this affects you test out the above port tarball! Otherwise, this will end up going in and not take into account any problems that might arise in your environment. Sorry, I missed the previous emails. The new mingw32-gcc seems to work flawlessly in my environment. I have found the mingw32-gcc port (a) very useful and (b) extremely impressive. Thanks. uname -a FreeBSD laptop3.gateway.2wire.net 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Feb 22 14:13:38 CST 2009 step...@laptop3.gateway.2wire.net:/usr/obj/usr/src/sys/LAPTOP3 amd64 Software compiled: http://www.math.missouri.edu/~stephen/software/spherical/ Stephen ___ 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
Fw: ports/126042: audio/festival: add OGI option
Hi Gerald; I haven´t checked this in a while but it was my attempt to clean Festival+OGI port that you just deprecated. cheers, Pedro. - Forwarded Message From: freebsd-gnats-sub...@freebsd.org freebsd-gnats-sub...@freebsd.org To: Pedro F. Giffuni pfgshield-free...@yahoo.com Sent: Monday, July 28, 2008 10:20:03 AM Subject: Re: ports/126042: audio/festival: add OGI option Thank you very much for your problem report. It has the internal identification `ports/126042'. The individual assigned to look at your report is: freebsd-ports-bugs. You can access the state of your problem report at any time via this link: http://www.freebsd.org/cgi/query-pr.cgi?pr=126042 Category: ports Responsible:freebsd-ports-bugs Synopsis: audio/festival: add OGI option Arrival-Date: Mon Jul 28 15:20:03 UTC 2008 ___ 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
