FreeBSD Port: refdb-0.9.8
Hi, this is just to let you know that a new upstream release 0.9.9-1 is available: http://sourceforge.net/project/showfiles.php?group_id=26091&package_id=19605&release_id=552558 I'll be happy to assist if there are any packaging problems that should be fixed upstream. regards, Markus -- Markus Hoenicka [EMAIL PROTECTED] (Spam-protected email: replace the quadrupeds with "mhoenicka") http://www.mhoenicka.de ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: augmenting a port: request for advice
Andriy Gapon wrote: on 07/12/2007 15:50 Andriy Gapon said the following: So I have this solution worth of Solomon's wisdom :-) It is to add an option to the port, say with WITH_FUSE. When the option is turned on the port would download my sources in addition to the original sources, then modify the build scripts, patch the original sources and build an additional program udfclientfs. Updating plist and dependencies would also be done, of course. http://www.freebsd.org/cgi/query-pr.cgi?pr=118484 Please comment. Here is an idea. I notice that the extra sources you want to download are rather small (about 7000 bytes when zipped). How about if you put the sources into the "files" subdirectory of the port itself, and then the port doesn't have to download anything extra. So, for example, the portlint port comes complete with full sources, adding up to nearly 100,000 bytes in its "files" subdirectory. So adding 7000 bytes to a port is going to be small by comparison. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (Very) bogus package dependencies
--On Friday, December 07, 2007 00:18:15 -0500 Alex Goncharov <[EMAIL PROTECTED]>, Alex Goncharov <[EMAIL PROTECTED]> wrote: I won't dispute the word "beauty" here -- I like the system very much. But coming from some eight years of using Debian, I am still mystified about the underling mechanics of ports. Your answers definitely help -- thank you! Any time you see USE_FOO= bar in a Makefile, the answer to what does that mean will be in /usr/ports/Mk/ somewhere. So grep USE_FOO in /usr/ports/Mk/* and you'll find where it appears. Then you can read the file and usually figure out what that means. You may then have to go read Makefiles for the ports to which it refers (in the case of cdrtools, cdrecord) and try to figure out why *that* port is required for "your" port to build. As maintainers, the first thing we have to do is read the requirements for the software and make sure those dependencies are built as well. So, for example, if a new port I'm working on requires that libdir is installed, I have to figure out whether it is or not, and if not, how I get it installed. Whenever possible, we try to use the port macros (USE_FOO), but if not, we have to use BUILD_DEPENDS to require that some other port is installed before ours begins the build. There are some wonderfully talented and highly knowledgeable people working behind the scenes to make sure all this stuff works in harmony, so I don't ask why, I just make sure my ports work as expected. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
augmenting a port: request for advice
There is a port, sysutils/udfclient, that I maintain. I also have some code (written by myself) that acts as a FUSE-glue (sysutils/fusefs-*) for udfclient, so that a UDF filesystem could be RW-accessed via the usual filesystem means (on RW media, of course). The thing is that the author of the udfclient code, Reinoud Zandijk, doesn't want to include my code into his program (for various good reasons). But he doesn't mind a bit against my code and there are no licensing problems. On the other hand, I also do not want to fork his code and/or distribute it under the hood of my code. So I have this solution worth of Solomon's wisdom :-) It is to add an option to the port, say with WITH_FUSE. When the option is turned on the port would download my sources in addition to the original sources, then modify the build scripts, patch the original sources and build an additional program udfclientfs. Updating plist and dependencies would also be done, of course. I think this should work, but I would like to get an advice, or even better, an example of an existing port on how to do something like this. Another small issue is that I currently don't have a reliable place to host my sources. I'll try to get it, but as a backup plan, I think there is some way to get my distfile hosted by FreeBSD itself, but I am not sure how to request for this. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: augmenting a port: request for advice
on 07/12/2007 15:50 Andriy Gapon said the following: > So I have this solution worth of Solomon's wisdom :-) > It is to add an option to the port, say with WITH_FUSE. When the option > is turned on the port would download my sources in addition to the > original sources, then modify the build scripts, patch the original > sources and build an additional program udfclientfs. Updating plist and > dependencies would also be done, of course. http://www.freebsd.org/cgi/query-pr.cgi?pr=118484 Please comment. -- Andriy Gapon ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: finding configuration options used
jekillen wrote: Hello: I am in the process of setting up Cyrus SASL for Postfix. Is there a way to determine what configuration options where used to build Cyrus SASL from port/package? Or would it be wise to de-install and reinstall with configuration options I am interested in? I am following various documentation sources for this: The Book of Postfix (No Starch Press) Postfix manual, and others relating to Cyradm. I am trying to get a handle on theory as well as practice so I have some vision. I did follow instruction from this list to rebuild postfix to include mysql support that worked fine. I am assuming that the make configure instruction could be employed with Cyrus SASL. The point being to have as many authentication methods as practically possible. And if a method is offered, it is actually supported. This is an educational project for me as well as setting up a working mail server. So far so good. But I have a long way to go before show time. using FreeBSD v6.2 Thanks in advance for info Jeff K I think Cyrus uses OPTIONS; try: $ cd /usr/ports/mail/cyrus-imapd23 && make showconfig HTH, Kevin Kinsey -- YEAR: A period of three hundred and sixty-five disappointments. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/98946: [patch] xscreensaver and PAM/kerberos support
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 If you're interested in xscreensaver support for pam and/or kerberos, please take a look at http://dougbarton.us/Downloads/xs-504-pam-kerberos.diff. You should apply the patch with the --remove-empty-files option. If I don't hear of any problems by the time the freeze is over, I plan to commit this update. Doug - -- This .signature sanitized for your protection -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.7 (FreeBSD) iD8DBQFHWkMAyIakK9Wy8PsRA2KsAKCc55EdulCMJX/ug8DuYGhZWdzujgCfWWOb O2DMYTwimk07A2gyARsZcEY= =uMLc -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: (Very) bogus package dependencies
,--- Garrett Cooper (Fri, 7 Dec 2007 15:42:38 -0800) * | Indeed. There's a lot of work put in by a lot of pkg/ports | maintainers to ensure that stuff works out of the box with as little | work / maintenance knowledge on the end-user portion as possible, and | in the long run not having to keep track of a billion different | options and/or other 'useless' information is the correct way to go | IMHO. `* ,--- You=Beech (Fri, 7 Dec 2007 15:22:43 -0900) * | Lets not forget the developers who make up portmgr. They support and | guide us also keeping the whole project going in the same (relative) | direction, insuring that all of the ports build and install in the | same way. This further lessens the burdon on users who "just want it | to work". They have the unenviable task of actually building close to | 90,000 ports for the new releases. They also actively maintain the | software that keeps track of all these dependencies. As you have seen | the dependencies from just one port can become complicated. Imagine | trying to map all 18,000 ports in the tree. Our system isn't perfect, | but it's constantly being improved. I am speaking as a relatively new (about two years, on and off) FreeBSD user -- a grateful user. It actually keeps amazing me how fast things move in into the ports collection once they are available anywhere in the world and how robust they are. A most recent example -- `xf86-video-radeonhd' package. Its (truly important for some video cards' users, like me) update made it into the ports on about the second day after it got available from SuSe (?) developers. It really changed my everyday experience, making a luxurious display work luxuriously, indeed. Same thing with `opera', `emacs' -- everything. So, if I may address the portmgr developers: Thank you! | I'll take our port/pkg system over any of the other *nix systems. Well, I just took it over Debian, as I mentioned, which I think can be taken over any of the other *nix package systems (FreeBSD ports/pkg excluded, of course ;-)... Thanks, -- Alex -- [EMAIL PROTECTED] -- /* * Shedenhelm's Law: * All trails have more uphill sections * than they have downhill sections. */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (Very) bogus package dependencies
Thank you Paul, ,--- You=Paul (Fri, 07 Dec 2007 09:41:25 -0600) * | There are some wonderfully talented and highly knowledgeable people working | behind the scenes to make sure all this stuff works in harmony, so I don't | ask why, I just make sure my ports work as expected. -- that I can see very clearly! Ports is a things of beauty, in my opinion. Not that it can be necessarily seen right away. Not that it can be mastered without an effort and errors :-) Thank you again for the extensive and helpful explanations! -- Alex -- [EMAIL PROTECTED] -- /* * There are two major products that come out of Berkeley: LSD and UNIX. * We don't believe this to be a coincidence. * * -- Jeremy S. Anderson */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (Very) bogus package dependencies
On Dec 7, 2007, at 7:41 AM, Paul Schmehl wrote: --On Friday, December 07, 2007 00:18:15 -0500 Alex Goncharov [EMAIL PROTECTED]>, Alex Goncharov <[EMAIL PROTECTED]> wrote: I won't dispute the word "beauty" here -- I like the system very much. But coming from some eight years of using Debian, I am still mystified about the underling mechanics of ports. Your answers definitely help -- thank you! I'm not sure about you, but I rather like not having 5~10 variants of the same package for every single option available at build-time :). Any time you see USE_FOO= bar in a Makefile, the answer to what does that mean will be in /usr/ports/Mk/ somewhere. So grep USE_FOO in /usr/ports/Mk/* and you'll find where it appears. Then you can read the file and usually figure out what that means. You may then have to go read Makefiles for the ports to which it refers (in the case of cdrtools, cdrecord) and try to figure out why *that* port is required for "your" port to build. As maintainers, the first thing we have to do is read the requirements for the software and make sure those dependencies are built as well. So, for example, if a new port I'm working on requires that libdir is installed, I have to figure out whether it is or not, and if not, how I get it installed. Whenever possible, we try to use the port macros (USE_FOO), but if not, we have to use BUILD_DEPENDS to require that some other port is installed before ours begins the build. Correct. The option was required at build-time and is a requirement for running the package (RUN_DEPENDS), which means that unfortunately it's required for installation too. There are some wonderfully talented and highly knowledgeable people working behind the scenes to make sure all this stuff works in harmony, so I don't ask why, I just make sure my ports work as expected. Indeed. There's a lot of work put in by a lot of pkg/ports maintainers to ensure that stuff works out of the box with as little work / maintenance knowledge on the end-user portion as possible, and in the long run not having to keep track of a billion different options and/or other 'useless' information is the correct way to go IMHO. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ Cheers, -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: augmenting a port: request for advice
On Dec 7, 2007, at 8:03 AM, Stephen Montgomery-Smith wrote: Andriy Gapon wrote: on 07/12/2007 15:50 Andriy Gapon said the following: So I have this solution worth of Solomon's wisdom :-) It is to add an option to the port, say with WITH_FUSE. When the option is turned on the port would download my sources in addition to the original sources, then modify the build scripts, patch the original sources and build an additional program udfclientfs. Updating plist and dependencies would also be done, of course. http://www.freebsd.org/cgi/query-pr.cgi?pr=118484 Please comment. Here is an idea. I notice that the extra sources you want to download are rather small (about 7000 bytes when zipped). How about if you put the sources into the "files" subdirectory of the port itself, and then the port doesn't have to download anything extra. So, for example, the portlint port comes complete with full sources, adding up to nearly 100,000 bytes in its "files" subdirectory. So adding 7000 bytes to a port is going to be small by comparison. No dice on that I think. It's artistic license, which means (AFAIK) that it can't be distributed with the ports tree as it's not BSD licensed code. -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (Very) bogus package dependencies
On Friday 07 December 2007, Garrett Cooper said: > On Dec 7, 2007, at 7:41 AM, Paul Schmehl wrote: > > --On Friday, December 07, 2007 00:18:15 -0500 Alex Goncharov > > , Alex Goncharov > > <[EMAIL PROTECTED]> > > > > wrote: > >> I won't dispute the word "beauty" here -- I like the system very > >> much. > >> But coming from some eight years of using Debian, I am still > >> mystified > >> about the underling mechanics of ports. > >> > >> Your answers definitely help -- thank you! > > I'm not sure about you, but I rather like not having 5~10 variants > of the same package for every single option available at build-time > :). > > > Any time you see USE_FOO= bar in a Makefile, the answer to what > > does that mean will be in /usr/ports/Mk/ somewhere. So grep > > USE_FOO in /usr/ports/Mk/* and you'll find where it appears. > > Then you can read the file and usually figure out what that > > means. You may then have to go read Makefiles for the ports to > > which it refers (in the case of cdrtools, cdrecord) and try to > > figure out why *that* port is required for "your" port to build. > > > > As maintainers, the first thing we have to do is read the > > requirements for the software and make sure those dependencies > > are built as well. So, for example, if a new port I'm working on > > requires that libdir is installed, I have to figure out whether > > it is or not, and if not, how I get it installed. Whenever > > possible, we try to use the port macros (USE_FOO), but if not, we > > have to use BUILD_DEPENDS to require that some other port is > > installed before ours begins the build. > > Correct. The option was required at build-time and is a requirement > for running the package (RUN_DEPENDS), which means that > unfortunately it's required for installation too. > > > There are some wonderfully talented and highly knowledgeable > > people working behind the scenes to make sure all this stuff > > works in harmony, so I don't ask why, I just make sure my ports > > work as expected. > > Indeed. There's a lot of work put in by a lot of pkg/ports > maintainers to ensure that stuff works out of the box with as > little work / maintenance knowledge on the end-user portion as > possible, and in the long run not having to keep track of a billion > different options and/or other 'useless' information is the correct > way to go IMHO. Lets not forget the developers who make up portmgr. They support and guide us also keeping the whole project going in the same (relative) direction, insuring that all of the ports build and install in the same way. This further lessens the burdon on users who "just want it to work". They have the unenviable task of actually building close to 90,000 ports for the new releases. They also actively maintain the software that keeps track of all these dependencies. As you have seen the dependencies from just one port can become complicated. Imagine trying to map all 18,000 ports in the tree. Our system isn't perfect, but it's constantly being improved. I'll take our port/pkg system over any of the other *nix systems. Beech -- --- Beech Rintoul - FreeBSD Developer - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.FreeBSD.org/releases/6.2R/announce.html --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
