Re: Give up maintainership
hideo schrieb: Alex Kiesel (Fri 02/23/07 16:51): sysutils/lxsplit sysutils/reoback I can take these two if you like. Sure. -Alex ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Give up maintainership
On Fri, Feb 23, 2007 at 09:48:29AM -0700, hideo wrote: > Alex Kiesel (Fri 02/23/07 16:51): > > sysutils/lxsplit > > sysutils/reoback > > I can take these two if you like. And you got it -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Give up maintainership
On Fri, Feb 23, 2007 at 04:51:49PM +0100, Alex Kiesel wrote: > I am the maintainer of the following ports: > > databases/freetds > databases/freetds-msdblib > databases/sqsh > databases/sybase_ase > devel/pecl-svn They are resetted now. If somebody wants to catch one of them, it's stil not too late! Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Give up maintainership
On Fri, Feb 23, 2007 at 07:16:46PM +0300, Alexander Zhuravlev wrote: > On Fri, Feb 23, 2007 at 04:51:49PM +0100, Alex Kiesel wrote: > > Hello Porters, > > > > I am the maintainer of the following ports: > > x11-toolkits/php-gtk > > I can take maintainership over this one. And you got it. -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Give up maintainership
On Fri, Feb 23, 2007 at 07:16:46PM +0300, Alexander Zhuravlev wrote: > On Fri, Feb 23, 2007 at 04:51:49PM +0100, Alex Kiesel wrote: > > Hello Porters, > > > > I am the maintainer of the following ports: > > x11-toolkits/php-gtk > > I can take maintainership over this one. And you got it. -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://weblog.barnet.com.au/edwin/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audacity needs a loving family
On Fri, 23 Feb 2007, Craig Boston wrote: I'm currently the maintainer for the Audacity port, however I haven't had much free time lately and it needs some attention. Previously I was in a position that I needed this software almost daily, however due to a chance in circumstances a while back I only rarely use it now. If there is anyone who feels like they have the time to dedicate to it and wants to take over maintainership please let me know. There's a few issues with it that need to be kept in mind and I'd like to make sure that information gets passed on. I'm cc-ing Jack as he maintains the audacity-devel port and may be interested. In the meantime I'm going to at least try to get the latest stable release working over the weekend (there's a PR about it with a patch but it didn't work on i386 when I tried). I don't want the port to be without a maintainer, so I'll keep it so long as nobody steps up, but can only make best-effort guarantees about timeliness. I'm not interested in maintainership of Audacity, but your post did bring up a thought. I think it would make sense to have a wiki for maintainers where they can keep notes, documentation and special circumstances information about ports. Add links to the definitive source of the code, a short history, a link to the CVS/SVN repository changelog, and as Craig mentioned above a listing of "a few issues ... that need to be kept in mind." This way even if Craig got hit by a beer truck (God forbid), the knowledge Craig gained during his maintainership would live on. One section per port, and ports could link to eachother (dependencies). A tool could be written that would generate the baseline documentation on the fly (or at least generated as text to be copied and pasted into the wiki to save time). A default template and instructions/guidelines would be strongly encouraged to keep the documentation consistent. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Optionally depending on one of two ports (or none of them)
Gabor Kovesdan <[EMAIL PROTECTED]> wrote:
> Fabian Keil schrieb:
> > Also by now my goal has been slightly changed and I want
> > to give the user the choice to either use one of the Tor
> > ports, or on none (if Tor is running on a remote system or
> > in another jail).
> >
> > The easiest solution is to not register any
> > dependencies and to simply print a pkg-message
> > to inform the user about his choices, but I was
> > wondering if there is a better way (that doesn't
> > involve shell scripts)?
> >
> > Simply adding OPTIONS is not an option (harhar) because
> > it wouldn't prevent the user from choosing the
> > wrong Tor port (the Tor ports use identical pkg-plists).
> What about grepping in the output of pkg_info? Or even better just
> grepping in ls ${PKG_DBDIR} to determine which one is installed and
> adding the appropriate dependency.
Are you aware of ports that already do that?
I grepped around a bit but didn't find any,
and as my make knowledge is rather limited
it sounds like too much work to be worth it.
Fabian
signature.asc
Description: PGP signature
Re: Optionally depending on one of two ports (or none of them)
Fabian Keil schrieb:
Gabor Kovesdan <[EMAIL PROTECTED]> wrote:
What about grepping in the output of pkg_info? Or even better just
grepping in ls ${PKG_DBDIR} to determine which one is installed and
adding the appropriate dependency.
Are you aware of ports that already do that?
I grepped around a bit but didn't find any,
and as my make knowledge is rather limited
it sounds like too much work to be worth it.
No, but I made an example for you, you can use this:
HAVE_TOR_DEVEL!=if ls /var/db/pkg | grep tor-devel-\* >/dev/null
2>&1 ; then echo YES; fi;
You should decide which one to use as a default. Let's say it is tor.
.if defined(HAVE_TOR_DEVEL)
RUN_DEPENDS+= ${LOCALBASE}/bin/tor:${PORTSDIR}/security/tor-devel
.else
RUN_DEPENDS+= ${LOCALBASE}/bin/tor:${PORTSDIR}/security/tor
.endif
Or if you want to make tor-devel the default one:
.if !defined(HAVE_TOR_DEVEL)
RUN_DEPENDS+= ${LOCALBASE}/bin/tor:${PORTSDIR}/security/tor
.else
RUN_DEPENDS+= ${LOCALBASE}/bin/tor:${PORTSDIR}/security/tor-devel
.endif
Or you can make it better by giving a knob for selecting the default.
The only problem is with my example, it does not respect PKG_DBDIR, but
I think it is better then just adding a pkg-message for the user to make
decision. I could not use ${PKG_DBDIR} in the evaluation somehow, it did
not work. This is not a big deal, though, people don't often override
that I think.
Regards,
Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Optionally depending on one of two ports (or none of them)
Fabian Keil wrote:
> I maintain the ports security/dns-proxy-tor and
> security/trans-proxy-tor which both require a Tor
> control port being available somewhere to do their job.
>
> They can work with both Tor versions in the ports collection
> (security/tor and security/tor-devel), and I originally wanted
> to register a dependency on the one that is already installed,
> or use tor-devel if no version is installed.
>
> To do that I added the RUN_DEPENDS line:
>
> ${LOCALBASE}/bin/tor:${PORTSDIR}/security/tor-devel
>
> which mostly works as expected, but fails if the tor
> port is installed, in which case a dependency on tor-devel
> is registered.
>
> I'm aware that my RUN_DEPENDS line is incorrect,
> but I'm unaware of a better way.
This is a bug in the ports framework. It wrongfully assumes, that an
installed binary X is/was provided by port Y if you specify X:Y.
What it _should_ do is check for binary X, if present use pkg_info -W to
get the right port. If not present, use Y as a default port to pull in
this binary.
The same thing happens, if you e.g. install lynx-ssl and some other port
depends on lynx (the binary!) then a dependancy on lynx (the port) will
be recorded, not on lynx-ssl.
It is trivial to fix, iff you assume that the user only installs
software via ports and all the databases are consistent.
Ulrich Spoerlein
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nvidia-driver does not compile again
Yesterday I deinstalled a fully functional x11/nvidia-driver (Version 9746) because I wanted to install the newest version of x11-servers/xorg-server (with imake.c patch). Installing of xorg-server works fine, but after that I am not able to compile the nvidia-driver any more. The following error occurs within nvidia_pci.c: - /usr/ports/x11/nvidia-driver# make && make install [...snip...] cc -O2 -fno-strict-aliasing -pipe -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVEL=9746 -D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -fno-common -msoft-float -fno-unit-at-a-time -minline-all-stringops -Werror -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -I- -I/src -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -c nvidia_pci.c nvidia_pci.c: In function `nvidia_pci_setup_intr': nvidia_pci.c:55: warning: passing arg 4 of `bus_setup_intr' from incompatible pointer type nvidia_pci.c:55: warning: passing arg 5 of `bus_setup_intr' from incompatible pointer type nvidia_pci.c:55: error: too few arguments to function `bus_setup_intr' *** Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-9746/src. *** Error code 1 Stop in /usr/ports/x11/nvidia-driver/work/NVIDIA-FreeBSD-x86-1.0-9746. *** Error code 1 Stop in /usr/ports/x11/nvidia-driver. *** Error code 1 Stop in /usr/ports/x11/nvidia-driver. - It seems that there is a problem with PCI interrupt handling. Does anybody else observe this? Are there any hints what to do next? I am working with FreeBSD 7.0-CURRENT from today on i386. Any help is greatly appreciated. Thanks in advance, Rainer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
WITHOUT_BSDPAN Option For The "perl5.8" Port?
Hi Everyone, I often find that the installed bsdpan-* pseudo-packages aren't of great use to me. Would it be possible to add a "WITHOUT_BSDPAN" config option for the perl5.8 port in order to neglect the installation of the BSDPAN modules? I looked at the Makefile for the port to see if I could do it myself but the BSDPAN references seem to be littered throughout, and I'm not particularly versed in the ports system to make a good attempt. Thanks in advance, Kurt Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
WITHOUT_BSDPAN Option For The "perl5.8" Port?
Hi Everyone, I often find that the installed bsdpan-* pseudo-packages aren't of great use to me. Would it be possible to add a "WITHOUT_BSDPAN" config option for the perl5.8 port in order to neglect the installation of the BSDPAN modules? I looked at the Makefile for the port to see if I could do it myself but the BSDPAN references seem to be littered throughout, and I'm not particularly versed in the ports system to make a good attempt. Thanks in advance, Kurt Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Optionally depending on one of two ports (or none of them)
Gabor Kovesdan wrote:
> HAVE_TOR_DEVEL!=if ls /var/db/pkg | grep tor-devel-\* >/dev/null
> 2>&1 ; then echo YES; fi;
[...]
> The only problem is with my example, it does not respect PKG_DBDIR, but
> I think it is better then just adding a pkg-message for the user to make
> decision. I could not use ${PKG_DBDIR} in the evaluation somehow, it did
> not work. This is not a big deal, though, people don't often override
> that I think.
Why not do it this way?
HAVE_TOR_DEVEL!= if pkg_info -I tor-devel-\* >/dev/null 2>&1 ; then echo YES; fi
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
signature.asc
Description: OpenPGP digital signature
Rejected posting to [EMAIL PROTECTED]
You are not authorized to send mail to the CIO list from your [EMAIL PROTECTED] account. You might be authorized to post to the list from another of your accounts, or perhaps when using another mail program configured to use a different e-mail address, but LISTSERV has no way to associate this other account or address with yours. If you need assistance or if you have any questions regarding the policy of the CIO list, please contact the list owners at [EMAIL PROTECTED] --- Begin Message --- The original message was received at Sat, 24 Feb 2007 14:39:20 -0500 from freebsd.org [217.218.132.74] - The following addresses had permanent fatal errors - [EMAIL PROTECTED] - Transcript of session follows - ... while talking to 82.130.121.163: 554 <[EMAIL PROTECTED]>... Mail quota exceeded 554 <[EMAIL PROTECTED]>... Service unavailable ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. The WatchGuard Firebox which protects your network detected a message which may not be safe. Cause : The message contains a virus. Content type : application/octet-stream File name: mail.zip Virus status : Worm.Mydoom.M Action : The Firebox deleted mail.zip. Your network administrator can not restore this attachment. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/. --- End Message --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Optionally depending on one of two ports (or none of them)
On Sat, Feb 24, 2007 at 07:13:01PM +, Matthew Seaman wrote: > Why not do it this way? > > HAVE_TOR_DEVEL!= if pkg_info -I tor-devel-\* >/dev/null 2>&1 ; then echo YES; > fi The problem with this approach is that you couple another shell invocation into 'make index'. As long as they are in individual ports, it's ok, but when we get them in the infrastructure, that's when things slow down. No, I don't have an alternative proposal. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audacity needs a loving family
On Sat, 2007-02-24 at 08:41 -0500, Peter Beckman wrote: > On Fri, 23 Feb 2007, Craig Boston wrote: > > I'm not interested in maintainership of Audacity, but your post did bring > up a thought. > > I think it would make sense to have a wiki for maintainers where they can > keep notes, documentation and special circumstances information about > ports. Add links to the definitive source of the code, a short history, > a link to the CVS/SVN repository changelog, and as Craig mentioned above a > listing of "a few issues ... that need to be kept in mind." This way even > if Craig got hit by a beer truck (God forbid), the knowledge Craig gained > during his maintainership would live on. One section per port, and ports > could link to eachother (dependencies). > Most of this information can be obtained already from cvs logs if people take the time to write informative PR descriptions (and we take the time to make informative commit messages). I typically cut and paste the relevant lines from an app's included ChangeLog into commit messages as well as my own notes now. I can then use freshports or `cvs log` to look at my port's history as can anyone else and get a pretty good idea of what's gone on over time. I think many other ports committers simply cut and paste PR descriptions as commit messages too. There are some things that are harder to keep track of through cvs logs like known issues but I don't see anything wrong with maintainers adding a "known issues" section to a port's pkg-descr. They can even add an "RCS:" line to it with a link to the site's code repo if they want. There are some other alternatives of course. In the OpenBSD ports tree maintainers often write their own README or README.OpenBSD for their ports. These files are typically open ended and include whatever info the maintainer deems relevant. Gentoo uses a ChangeLog file in portage for each app. This is in part because each program version has its own ebuild file so change history is not preserved across program versions by the ebuild file. Maybe people might find the addition of an optional README.FreeBSD or ChangeLog file useful as a coherent record of the port and maintainer's work? tom -- | tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org | | FreeBSD http://www.FreeBSD.org | | BSD#http://www.mono-project.com/Mono:FreeBSD | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audacity needs a loving family
Tom McLaughlin wrote: On Sat, 2007-02-24 at 08:41 -0500, Peter Beckman wrote: On Fri, 23 Feb 2007, Craig Boston wrote: I'm not interested in maintainership of Audacity, but your post did bring up a thought. I think it would make sense to have a wiki for maintainers where they can keep notes, documentation and special circumstances information about ports. Add links to the definitive source of the code, a short history, a link to the CVS/SVN repository changelog, and as Craig mentioned above a listing of "a few issues ... that need to be kept in mind." This way even if Craig got hit by a beer truck (God forbid), the knowledge Craig gained during his maintainership would live on. One section per port, and ports could link to eachother (dependencies). Most of this information can be obtained already from cvs logs if people take the time to write informative PR descriptions (and we take the time to make informative commit messages). I typically cut and paste the relevant lines from an app's included ChangeLog into commit messages as well as my own notes now. I can then use freshports or `cvs log` to look at my port's history as can anyone else and get a pretty good idea of what's gone on over time. I think many other ports committers simply cut and paste PR descriptions as commit messages too. There are some things that are harder to keep track of through cvs logs like known issues but I don't see anything wrong with maintainers adding a "known issues" section to a port's pkg-descr. They can even add an "RCS:" line to it with a link to the site's code repo if they want. There are some other alternatives of course. In the OpenBSD ports tree maintainers often write their own README or README.OpenBSD for their ports. These files are typically open ended and include whatever info the maintainer deems relevant. Gentoo uses a ChangeLog file in portage for each app. This is in part because each program version has its own ebuild file so change history is not preserved across program versions by the ebuild file. Maybe people might find the addition of an optional README.FreeBSD or ChangeLog file useful as a coherent record of the port and maintainer's work? tom Either that or a common resource where the maintainer could submit changelogs and then users can look up the info... maybe a changelog feature on the FreeBSD ports site? -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: WITHOUT_BSDPAN Option For The "perl5.8" Port?
On Sat, Feb 24, 2007 at 10:44:10AM -0800, Kurt Abahar wrote: > I often find that the installed bsdpan-* > pseudo-packages aren't of > great use to me. Would it be possible to add a > "WITHOUT_BSDPAN" > config option for the perl5.8 port in order to neglect > the installation of the BSDPAN modules? I looked at > the Makefile for > the port to see if I could do it myself but the BSDPAN > references > seem to be littered throughout, and I'm not > particularly versed in > the ports system to make a good attempt. BSDPAN itself understands environment variable DISABLE_BSDPAN (meaning it does not do anything if this variable is set). It won't prevent BSDPAN from installing, but hopefully it will be able to help you. \Anton. -- We're going for 'working' here. 'clean' is for people with skills... -- Flemming Jacobsen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audacity needs a loving family
If the port is up for grabs, I'll take maintainership. I do use it from time to time. Cheers, Beech -- --- Beech Rintoul - Port Maintainer - [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 --- pgpr8ypMZg8Yy.pgp Description: PGP signature
http://leet.110mb.com The latest bussiness idea !
Hello ! We are sorry if we distrubed you . Your email is in our email bank . We found out that you are an active bussiness man ,so we were wondering of you are interested in a bussiness offer . If so , please check out site for all the info. http://leet.110mb.com We apologise again if this e-mail bottered you in anyway . Thank you ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
http://leet.110mb.com The latest bussiness idea !
Hello ! We are sorry if we distrubed you . Your email is in our email bank . We found out that you are an active bussiness man ,so we were wondering if you are interested in a bussiness idea . If so , please check out site for all the info. http://leet.110mb.com We apologise again if this e-mail bottered you in anyway . Thank you ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
openvpn-2.0.6_5 doesn't startup automatically after recent udpate
Greetings, I update my ports weekly. I have been using openvpn for two years now. After updating my openvpn port to openvpn-2.0.6_5 it does not start up by itself anymore. I havent change anything in my rc.conf nor in my /usr/local/etc/ openvpn. My configuration hasn't changed for the past two years. I checked UPDATING but there are no comments on openvpn. Any ideas? Thanks, Bazzool P.S CC me I am not subscribed to this list. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audacity needs a loving family
My 0.02 In my case, I write a blog with all my notes about the process of maintaining a port. I am very newbie in the process, but I want to leave something for anybody who is thinking in adopting/updating a port. I think a wiki or any other place where a maintainer can out his/her knowledge and expertice it is a great idea for eveybody who is involved or thinking about it. Alfredo On 2/24/07, Beech Rintoul <[EMAIL PROTECTED]> wrote: If the port is up for grabs, I'll take maintainership. I do use it from time to time. Cheers, Beech -- --- Beech Rintoul - Port Maintainer - [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]"
Re: [Bsd-sharp-list] [ports/lang/mono] crosstalk compiling problem between installed mono and port's mono
On Wed, 2007-02-21 at 17:41 +, [EMAIL PROTECTED] wrote: > > On Wed, Feb 21, 2007 at 01:48:44PM -0300, Phillip Neumann wrote: > >> El mi??, 21-02-2007 a las 17:28 +0200, Kostik Belousov escribi??: > >> > Could you, please, give me the full patch (against CVS Makefile) ? > >> > >> > >> Sure. sorry for not doing it .. > >> > >> thanks > >> > > > > Patch helped, thanks. I successfully did portupgrade -f mono-1.2.2.1_2. > > > > Gah, I didn't realize in my earlier patch that MAKE_ENV was redefined a > little further below in the port's Makefile. I'm still curious to know > what the exact change was that fixed things. (It may be that while one > change fixed your problem we should be using all the changes so we don't > get bitten again later.) I'll commit Philip's patch later when I have > access. > > tom This was really weird. The exact change needed was adding LC_ALL=C to MAKE_ENV. That resolved the problem on mux@'s machine. Odd thing was I was never able to reproduce this on his machine after using his LC environment settings. Anyways, it's committed so all should be fine now. Let me know if it's still broke for anyone. And thanks to everyone who tested changes for me. tom -- | tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org | | FreeBSD http://www.FreeBSD.org | | BSD#http://www.mono-project.com/Mono:FreeBSD | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New portmaster with -o and other fixes
On 2/23/07, Doug Barton <[EMAIL PROTECTED]> wrote: New Feature === --clean-distfiles[-all] options to check /usr/ports/distfiles for stale stuff, and either offer to delete them or delete them all without prompting. Thanks for your hardwork, this is a very nice feature to have (the lack of it is enough for me to keep the portupgrade suite). Jiawei Ye -- "If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Libmap issue with archivers/rar?
Hi: I used to have rar working just fine, but recently I tried using it and ran into the following: $ rar /libexec/ld-elf.so.1: Shared object "libstdc++.so.5" not found, required by "rar" I'm not sure what I may have done to break this, but I'm assuming it's an issue with my libmap.conf? FreeBSD belle.0lsen.net 5.5-STABLE FreeBSD 5.5-STABLE #1: Mon Oct 23 13:04:36 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BELLE i386 Thanks, -Clint ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New portmaster with -o and other fixes
Craig Boston wrote: Log: New Feature === --clean-distfiles[-all] options to check /usr/ports/distfiles for stale stuff, and either offer to delete them or delete them all without prompting. That's excellent news! Now I can use -D during upgrades to avoid pausing between port builds, and run this later to manually clean up the distfiles. *nod* I don't want to change the default, but I think that portmaster -aD will become a lot more popular. :) I'm a bit paranoid about automatically deleting them -- had one too many times when port[master|upgrade|foo] got confused by slave ports or weird file names and deleted hard to replace* distfiles. I think that you'll find the method I'm using for the --clean-distfiles option a lot safer, since it relies on the distinfo files. I'm torn about what to do with the distfile purging routines that are already in there for individual upgrades. On the one hand, the fact that they are aggressive pretty much guarantees that they will find any old distfiles related to a given port. On the other hand, that aggressiveness can be annoying, and/or dangerous. Thanks again for your work on portmaster! Thanks for the kind words. :) Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX build failed for 5.x
INDEX build failed with errors: Generating INDEX-5 - please wait..horde-passwd-3.0_2: "/local0/tmp/erwin/tindex/ports/www/horde" non-existent -- dependency list incomplete ===> www/horde-passwd failed *** Error code 1 *** Error code 1 Stop in /local0/tmp/erwin/tindex/ports. *** Error code 1 Stop in /local0/tmp/erwin/tindex/ports. 1 error Committers on the hook: db linimon rafan sat tmclaugh Most recent CVS update was: U MOVED U audio/exaile/Makefile U audio/exaile/distinfo U audio/exaile/pkg-plist U comms/fldigi/Makefile U comms/fldigi/distinfo U comms/fldigi/files/patch-makefile U comms/hamlib/Makefile U comms/hamlib/distinfo U comms/hamlib/files/patch-bindings_Makefile.in U comms/hamlib/files/patch-libltdl_configure U comms/hamlib/files/patch-macros_libtools.m4 U comms/wsjt/Makefile U comms/wsjt/files/patch-configure U comms/wsjt/files/patch-cutil.c U comms/wsjt/files/patch-get_fname.F90 U comms/wsjt/files/patch-jtaudio.c U comms/wsjt/files/patch-padevsub.c U comms/wsjt/files/patch-specjt.py U comms/wsjt/files/patch-wsjt.py U deskutils/kronolith/Makefile U deskutils/mnemo/Makefile U deskutils/nag/Makefile U devel/chora/Makefile U devel/p5-Term-Shell/Makefile U devel/p5-Term-Shell/distinfo U ftp/gollem/Makefile U lang/mono/Makefile U lang/mono/files/patch-mono_io-layer_shared.c U mail/imp/Makefile U mail/ingo/Makefile U mail/mimp/Makefile U mail/turba/Makefile U security/jeta/Makefile U www/Makefile U www/horde-base/Makefile ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
