[INFO] Current nvidia-driver 195.36.15
Hi guys! A couple weeks ago I was updated KDE to 4.4. But there I had not noticed, x11 and drivers were are updated too (portupgrade -aR). ;-) Okay, KDE was loaded and works okay! But! About 3-5 mins machine begins rebooted or halted unexpectedly. Hmm... I had spent some days to search what's the problem. I have P4 with Nvidia GeForce7600 card and current x11/nvidia-driver 195.36.15 does not work correctly. I reinstalled with old legacy driver 173.14.25 from ports and now all works are okay! ;-) -- Best regards, Alexey Serebryakoff signature.asc Description: This is a digitally signed message part.
Re: commit PR ports/146582: [PATCH]textproc/libxml2
On 22.06.2010 19:11, Chris Rees wrote: On 22 June 2010 15:21, Alexander Kriventsova...@vl.ru wrote: Hello! Can anybody commit this http://www.freebsd.org/cgi/query-pr.cgi?pr=146582? You need to ask the Gnome team to approve it first. How can I do this? They didn't send any replay from May 14. Is it possible to commit with reason like 'maintainer timeout'? This PR is only add option that allow to configure libxml without threads which is enable by default. Chris ___ 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
New pkg-message[.in] guideline idea
Hi freebsd-ports@, I would like to propose you something that I would like to be done. It's a cosmetic, useless thing but I like when things are made homogeneously. That is the problem : as you can see, sometimes port tells a message to the user but some maintainers used delimiters to begin/end the message such as a lot of *** or === or blank spaces. If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE is composed like this : === $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $ Note you need audio/audacious-plugins to actually play music. === I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I know that there is much more important work to do, that's why I can take all this work for myself. Please report any feedback, With kind regards. -- Demelier David ___ 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
scamp-5.2i
Hello all, I have updated scamp on my mailscanner machines. But after the update scamp does not work anymore. I also did delete the default config file, and thenscamps as kif i want to create a new one. But after the creation of the file nothing happens also a scamp -h does not show anything. This is on all my machines. Reverting scamp back all Works again. regards, Johan Hendriks ___ 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: New pkg-message[.in] guideline idea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/23/10 14:00, Ion-Mihai Tetcu wrote: On Wed, 23 Jun 2010 14:16:07 +0200 David DEMELIER demelier.da...@gmail.com wrote: Hi freebsd-ports@, I would like to propose you something that I would like to be done. It's a cosmetic, useless thing but I like when things are made homogeneously. That is the problem : as you can see, sometimes port tells a message to the user but some maintainers used delimiters to begin/end the message such as a lot of *** or === or blank spaces. If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE is composed like this : === $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $ Note you need audio/audacious-plugins to actually play music. === I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I know that there is much more important work to do, that's why I can take all this work for myself. Please report any feedback, With kind regards. Go ahead please. You'll need to keep the patch in sync for some time, so use CVS to make the patch. Ping me when you are ready. I am interested in this as well. If I can be of assistance I will. - -- - 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iD8DBQFMIhv5dbiP+9ubjBwRAu8NAJ9Vw255Xhi5n6U3D7YwkV4DctgSjACeLYA7 xZqXsFPmLkOHVN2lyEUOSJc= =w85t -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: New pkg-message[.in] guideline idea
On Wed, Jun 23, 2010 at 02:16:07PM +0200, David DEMELIER wrote: Hi freebsd-ports@, I would like to propose you something that I would like to be done. It's a cosmetic, useless thing but I like when things are made homogeneously. That is the problem : as you can see, sometimes port tells a message to the user but some maintainers used delimiters to begin/end the message such as a lot of *** or === or blank spaces. If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE is composed like this : === $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $ Note you need audio/audacious-plugins to actually play music. === I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I know that there is much more important work to do, that's why I can take all this work for myself. I think a better solution is to do what portmaster does and display all the pkg-message files as one of the last things it does. I had a patch to do this sitting in portmgr@ queue but it needs more work. A combination of some standardization of pkg-message files and displaying them all at the end of a build would be best. -- WXS ___ 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: scamp-5.2i
On Wed, 23 Jun 2010 16:23:57 +0200 Johan Hendriks jo...@double-l.nl articulated: Hello all, I have updated scamp on my mailscanner machines. But after the update scamp does not work anymore. I also did delete the default config file, and thenscamps as kif i want to create a new one. But after the creation of the file nothing happens also a scamp -h does not show anything. This is on all my machines. Reverting scamp back all Works again. regards, I am aware of the problem. An updated script was submitted: ports/147840: Updated Port: security/scamp I am awaiting its release. The problem was that a piece of debug code was inadvertently left in the version that was released. There was an exit code left over from a debug session. It was left on or about line 715 if I remember correctly. You could update to the latest ports version and just comment out that line, or wait for the new version to be released into the ports system. That is the last time I ever release anything late at night. -- Jerry ✌ freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ If you think the United States has stood still, who built the largest shopping center in the world? Richard M. Nixon ___ 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: New pkg-message[.in] guideline idea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/23/10 14:40, Wesley Shields wrote: On Wed, Jun 23, 2010 at 02:16:07PM +0200, David DEMELIER wrote: Hi freebsd-ports@, I would like to propose you something that I would like to be done. It's a cosmetic, useless thing but I like when things are made homogeneously. That is the problem : as you can see, sometimes port tells a message to the user but some maintainers used delimiters to begin/end the message such as a lot of *** or === or blank spaces. If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE is composed like this : === $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $ Note you need audio/audacious-plugins to actually play music. === I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I know that there is much more important work to do, that's why I can take all this work for myself. I think a better solution is to do what portmaster does and display all the pkg-message files as one of the last things it does. I had a patch to do this sitting in portmgr@ queue but it needs more work. A combination of some standardization of pkg-message files and displaying them all at the end of a build would be best. Yes thats definitely a needed feature. I think we need 2 things: 1) All pkg-message whether .in or not go through the 'sed' that SUB_LIST/PLIST_SUB do. 2) You collect them in to /var/db/pkg and loop and display at end. As a consequence all formatting should be removed from the individual pkg-message[.in] files and added in #2. Ideally I'd say we should just slowly switch everything to FILESDIR/pkg-message[.in] but portmgr@ already veto'd that before so I'll drop that idea. - -- - 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iD8DBQFMIh4ydbiP+9ubjBwRAix1AKCK76puppTw5UC3bWBS3t+zkQ+W/wCfWsPo GoWKEF6l7lZZABMYeynZHAs= =N0Vw -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: scamp-5.2i
That is the last time I ever release anything late at night. -- Jerry ✌ freebsd-ports.u...@seibercom.net Thanks for the update, i will wait for the new version to hit the tree. When doing things late, make sure there is enough coffee! :) thanks again for your time and effort maintaining this port. regards Johan Hendriks ___ 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
minidlna: a new port needs testers, start-up script
Hello! Digital Life Network Alliance http://en.wikipedia.org/wiki/DLNA is a standard newer than UPnP -- some devices on the market are not satisfied with plain UPnP-servers like mediatomb http://www.freshports.org/net/mediatomb... As far as I understand, the only DLNA-capable server ported to FreeBSD right now is ushare http://www.freshports.org/net/ushare, but it seems to require a full rescan of one's media-collection upon every startup... I (almost) ported a promising little DLNA-server http://minidlna.sourceforge.net/ (which uses SQLite3 database to store the collection data between restarts), but I need help with the start-up script http://www.freebsd.org/doc/en/books/porters-handbook/book.html#RC-SCRIPTS -- the server should run as its own unprivileged user:group (dlna:dlna), send stderr/stdout to /var/log/minidlna.log (I may later patch it to use syslog instead), and maintain PID-file in /var/run/minidlna.pid. The port can be downloaded from: http://aldan.algebra.com/~mi/minidlna-port.shar Both my Bravia TV and Onkyo receiver are able to play MP3 files served by it (although Onkyo can't decode the Cyrillics in the titles)... The TV can also show pictures (except for /progressive/ JPEGs, which Sony's JPEG implementation infamously rejects http://www.amazon.com/review/R2U4XPXENWU9BC/ref=cm_cr_rdp_perm). I'm yet to figure out, what video-file format the TV would accept -- minidlna does not offer on-the-fly transcoding... Also, some bug in avformat breaks it for certain .m2ts files I have (both ushare and ffplay suffer from the same). Please, report any problems by private e-mail. As soon as the start-up script is contributed, I'll commit the port. Thanks! -mi P.S. Before installing the port, remember to add the dlna user and group to /usr/ports/UIDs and /usr/ports/GIDs: --- UIDs12 Jun 2010 17:43:50 - 1.115 +++ UIDs23 Jun 2010 15:07:54 - @@ -173,2 +173,3 @@ nslcd:*:928:928::0:0:nslcd daemon:/nonexistent:/usr/sbin/nologin activemq:*:929:929::0:0:ActiveMQ Daemon:/nonexistent:/sbin/nologin +dlna:*:930:930::0:0:DLNA server:/nonexistent:/sbin/nologin --- GIDs12 Jun 2010 01:05:53 - 1.99 +++ GIDs23 Jun 2010 15:07:54 - @@ -163,2 +163,3 @@ nslcd:*:928: activemq:*:929: +dlna:*:930: ___ 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: nvidia-driver 256.35 released
On Wed, 23 Jun 2010, Alexey Dokuchaev wrote: On Tue, Jun 22, 2010 at 08:30:54PM -0500, Sam Fourman Jr. wrote: 2010/6/22 Alexey Dokuchaev da...@freebsd.org: *snip* Sure, I will take care of plist issues upon the upgrade. What is more important right now is driver stability issues people had been having. I must rely on other people testing since I was not able to reproduce most of them in my local environment. So what exactly do I have to do to test this? in the Makefile just -DISTVERSION?= 195.36.24 +DISTVERSION?= 256.35 I would suggest to start with 195.36.31, as 256.xx are early betas. Ideally, I want a stable version in 195.36.yy series before start looking at upcoming 256 ones. The 195.36.24/amd64 driver gives me no additional problems over 195.36.15 (current version in port) for a GeForce 8800 GTS. I see no 195.36.31 for amd64 available from nVidia. Since the amd64 versions were beta until the 256 series, Zander was blessing us--thank you!--with releases of it. [1] Sean 1. http://www.nvnews.net/vbulletin/showthread.php?t=150672 -- s...@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: New pkg-message[.in] guideline idea
On Wed, 23 Jun 2010, David DEMELIER wrote: I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I find it completely useless and plainly stupid to edit the pkg-messages of all ports to include lots of equal signs for tty-based formatting purposes. In my opinion the messages in the ports tree should contain (English language, word based) messages, and if some visual formatting is desired, it should be done by the upper layer which displays the message (such as the ports framework, a web site which displays information about various ports, or whatever). The more clueful web monkeys have known to separate content from visual formatting for several years, why should FreeBSD make the same mistake the web monkeys did when www first became popular? However I fully support the idea that all the relevant messages should be displayed at the end of a build/upgrade process whenever technically feasible (otherwise they will just fly past while I am having a lunch or whatever). If the boild/upgrade process fails in the middle, the messages of successful builds/upgrades should still be displayed, even though the end of the process has not been reached. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.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: nvidia-driver 256.35 released
On Wed, 2010-06-23 at 01:09 +, Alexey Dokuchaev wrote: Sure, I will take care of plist issues upon the upgrade. What is more important right now is driver stability issues people had been having. I must rely on other people testing since I was not able to reproduce most of them in my local environment. ./danfe Well, I can't comment on the stability issues as I didn't have any, but if it helps, just a quick success report to the pool: Latest 7.3-STABLE, i386, 256.35 on GeForce GT240: Tested pretty much everything from native OpenGL, through linuxulated games (Quake 4, ET), vdpau acceleration, DirectX-to-OpenGL translated Windows games through Wine, and finally some native Windows OpenGL through VirtualBox (whose current OpenGL implementation is pretty flaky on its own anyway), and so far, everything seems to be working rock solid, here and there with some minor performance increases. Could have been much worse, I guess. m. -- Michal Varga, Stonehenge (Gmail account) ___ 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: New pkg-message[.in] guideline idea
2010/6/23 Janne Snabb sn...@epipe.com: On Wed, 23 Jun 2010, David DEMELIER wrote: I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I find it completely useless and plainly stupid to edit the pkg-messages of all ports to include lots of equal signs for tty-based formatting purposes. In my opinion the messages in the ports tree should contain (English language, word based) messages, and if some visual formatting is desired, it should be done by the upper layer which displays the message (such as the ports framework, a web site which displays information about various ports, or whatever). We can take a long time to do that (we don't have to do it quickly), but it could be useful to standardize it for one reason : You will see that it's a message from the port maintainer/submitter and not from the program itself! Sometimes configure scripts stage say some useless things to the user. The more clueful web monkeys have known to separate content from visual formatting for several years, why should FreeBSD make the same mistake the web monkeys did when www first became popular? However I fully support the idea that all the relevant messages should be displayed at the end of a build/upgrade process whenever technically feasible (otherwise they will just fly past while I am having a lunch or whatever). If the boild/upgrade process fails in the middle, the messages of successful builds/upgrades should still be displayed, even though the end of the process has not been reached. I agree too. -- Demelier David ___ 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: New pkg-message[.in] guideline idea
On 06/23/10 07:46, Philip M. Gollucci wrote: On 06/23/10 14:40, Wesley Shields wrote: On Wed, Jun 23, 2010 at 02:16:07PM +0200, David DEMELIER wrote: Hi freebsd-ports@, I would like to propose you something that I would like to be done. It's a cosmetic, useless thing but I like when things are made homogeneously. I admit that my initial reaction was mixed in the sense that I don't like removing the ability of maintainers to be creative without good reason. However after thinking about this (and reviewing the other posts) I think that the benefits of being consistent so that the user knows what is a message and what is not are worth it. That is the problem : as you can see, sometimes port tells a message to the user but some maintainers used delimiters to begin/end the message such as a lot of *** or === or blank spaces. If you already did use NetBSD pkgsrc, you can see that *every* MESSAGE is composed like this : === $NetBSD: MESSAGE,v 1.1.1.1 2008/10/20 09:28:51 wiz Exp $ Not to dive too quickly into the details, but I would see no value in actually displaying the CVS $Id to the user. :) Note you need audio/audacious-plugins to actually play music. === I would do something like this to the FreeBSD ports, if you agree with me I can check every messages and modify them. I can also put something in the FreeBSD porter's handbook to write a pkg-message template I know that there is much more important work to do, that's why I can take all this work for myself. That's great! When I first started in FreeBSD I wasn't new to programming but I was new to Unix, and taking on projects like this was a great way to get involved, give back to the community, and learn more about the system. I think a better solution is to do what portmaster does and display all the pkg-message files as one of the last things it does. I had a patch to do this sitting in portmgr@ queue but it needs more work. FWIW, portmaster users have commented to me many times that this is one of their favorite features, and that they find it very useful. So much so that I wish it were my idea, but it actually came from a user. :) I think it would be great if the ports infrastructure were able to do this as well. A combination of some standardization of pkg-message files and displaying them all at the end of a build would be best. Yes thats definitely a needed feature. I think we need 2 things: 1) All pkg-message whether .in or not go through the 'sed' that SUB_LIST/PLIST_SUB do. I like this idea better than forcing them all to be in /files, and I can't see any reason not to do it. 2) You collect them in to /var/db/pkg and loop and display at end. As a consequence all formatting should be removed from the individual pkg-message[.in] files and added in #2. I'm ambivalent about this. My first thought was that the formatting should happen in step #1. What portmaster does is build each port one at a time, and it makes a note if a port has a pkg-message. Then it does what you suggest in #2 by cat'ing them all to $PAGER. However, thinking more about it I could see how not doing the formatting until step 2 could work, so however it turns out to be easiest should be fine. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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: New pkg-message[.in] guideline idea
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/23/10 19:15, Doug Barton wrote: I think we need 2 things: 1) All pkg-message whether .in or not go through the 'sed' that SUB_LIST/PLIST_SUB do. I like this idea better than forcing them all to be in /files, and I can't see any reason not to do it. The other benefit is you can carry over the PLIST logic with @comment to conditionalize lines in the message and thus eliminate all that crap from Makefiles. 2) You collect them in to /var/db/pkg and loop and display at end. As a consequence all formatting should be removed from the individual pkg-message[.in] files and added in #2. I'm ambivalent about this. My first thought was that the formatting should happen in step #1. What portmaster does is build each port one at a time, and it makes a note if a port has a pkg-message. Then it does what you suggest in #2 by cat'ing them all to $PAGER. However, thinking more about it I could see how not doing the formatting until step 2 could work, so however it turns out to be easiest should be fine. I believe we are agreeing. I didn't say anything about portmaster/portupgrade. The pkg/make infrastructure needs to do it at the end so that it works via pkg_add, make, or portmaster et al. - -- - 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354 VP Apache Infrastructure; Member, Apache Software Foundation Committer,FreeBSD Foundation Consultant, P6M7G8 Inc. Sr. System Admin, Ridecharge Inc. Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iD4DBQFMIl5KdbiP+9ubjBwRApYMAJ0ZgYpsSy41WeNNZxKjpgK2HpKdcwCYh54j 7t2X4DuUUkkrAdeLTr2Kiw== =BrZx -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: New pkg-message[.in] guideline idea
On 06/23/10 12:19, Philip M. Gollucci wrote: On 06/23/10 19:15, Doug Barton wrote: I think we need 2 things: 1) All pkg-message whether .in or not go through the 'sed' that SUB_LIST/PLIST_SUB do. I like this idea better than forcing them all to be in /files, and I can't see any reason not to do it. The other benefit is you can carry over the PLIST logic with @comment to conditionalize lines in the message and thus eliminate all that crap from Makefiles. Yes, simpler is better. :) 2) You collect them in to /var/db/pkg and loop and display at end. As a consequence all formatting should be removed from the individual pkg-message[.in] files and added in #2. I'm ambivalent about this. My first thought was that the formatting should happen in step #1. What portmaster does is build each port one at a time, and it makes a note if a port has a pkg-message. Then it does what you suggest in #2 by cat'ing them all to $PAGER. However, thinking more about it I could see how not doing the formatting until step 2 could work, so however it turns out to be easiest should be fine. I believe we are agreeing. I didn't say anything about portmaster/portupgrade. The pkg/make infrastructure needs to do it at the end so that it works via pkg_add, make, or portmaster et al. Yes, we are agreeing. I was simply adding my perspective as a tool author to your proposal. I also agree that the ports infrastructure itself should be as robust as possible, and include features like this whenever it can. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!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: New pkg-message[.in] guideline idea
On Wed, 23 Jun 2010 18:28:22 +0200 David DEMELIER demelier.da...@gmail.com wrote: Because I always used mv, vim, diff to generate patches I need some time to learn the way to do patches with cvs. http://ionut.tetcu.info/FreeBSD/How-to-submit-a-diff.txt HTH, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: New pkg-message[.in] guideline idea
On Wed, 23 Jun 2010, David DEMELIER wrote: 2010/6/23 Janne Snabb sn...@epipe.com: I find it completely useless and plainly stupid to edit the pkg-messages of all ports to include lots of equal signs for tty-based formatting purposes. We can take a long time to do that (we don't have to do it quickly), but it could be useful to standardize it for one reason : You will see that it's a message from the port maintainer/submitter and not from the program itself! Sometimes configure scripts stage say some useless things to the user. You obviously did not get my point. I fully agree with you that displaying a line of equals signs on tty based interfaces to make the messages stand out from other crap when installing ports makes sense, but I STRONGLY oppose to the idea of putting this visual formatting in the actual message files. It is just not the right place to put it in. As I pointed out in my previous message, these messages are displayed by various different means for different purposes by different pieces of software (on tty, through GUI, on web sites, etc). Some of that software does not exist right now, but may be implemented in future (I am thinking here of for example a Synaptic like tool for managing the installed software). A line of equals signs looks good on a 80 character wide tty screen when the important message is surrounded by other non-important output, but it just looks stupid when displayed by a GUI or on a web site. Putting the visual cues in pkg-messages files would require every other display mechanism to have a logic to strip them out (for example when displaying the message on X display as a word-wrapped pop-up-window of random width). Why not just change the current display logic to emit these visual cues on a tty when installing ports? It is a single edit to a single file and does not introduce useless clutter in approximately 2209 pkg-message* files in the ports tree. I do realize that many of the current pkg-messages do include similar visual visual formatting already in a non-standard way. One port uses equals signs, another port uses hyphens, etc. Those should be all removed from pkg-messages when the ports infrastructure displays a standardized visual separator automatically. I do not oppose to the other related ideas (such as making a logic to optionally display a part of a message only when some option was enabled). -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.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
