Re: New pkg-message[.in] guideline idea
On Thu, Jun 24, 2010 at 12:04 AM, David DEMELIER demelier.da...@gmail.com wrote: 2010/6/24 Janne Snabb sn...@epipe.com: 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. I see, so maybe in the future you would like some tools that can print the message, like a GTK+ dialog, QT dialog, or an other tool, if it's your point I agree. I don't specially want a equal == line, I would just something consistent, why not : nothing ? Yes we can just print the text without any visual characters, and the [future] tool will print the message as it want. No, what he's saying is: - put the logic to print the separators into the appropriate bsd.*.mk file - remove all separators from all pkg-message* files That way, you can update the separators at any time by editing a single file, instead of editing 20,000+ pkg-message files. And, that way, future tools can override the separator set in the mk file. Leave the pkg-message files as unformatted text. Put the formatting into the mk file. Separate content from style. -- Freddie Cash fjwc...@gmail.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 Thu, Jun 24, 2010 at 9:43 AM, David DEMELIER
demelier.da...@gmail.com wrote:
2010/6/24 Freddie Cash fjwc...@gmail.com:
On Thu, Jun 24, 2010 at 12:04 AM, David DEMELIER
demelier.da...@gmail.com wrote:
2010/6/24 Janne Snabb sn...@epipe.com:
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.
I see, so maybe in the future you would like some tools that can print
the message, like a GTK+ dialog, QT dialog, or an other tool, if it's
your point I agree. I don't specially want a equal == line, I would
just something consistent, why not : nothing ? Yes we can just print
the text without any visual characters, and the [future] tool will
print the message as it want.
No, what he's saying is:
- put the logic to print the separators into the appropriate bsd.*.mk file
- remove all separators from all pkg-message* files
That way, you can update the separators at any time by editing a
single file, instead of editing 20,000+ pkg-message files. And, that
way, future tools can override the separator set in the mk file.
Leave the pkg-message files as unformatted text. Put the formatting
into the mk file.
Separate content from style.
Yes, that was I said, sorry if you did not understand well :-)
The only problem is that pushing all of this logic into bsd.*.mk only
solves half the problem: from source installations. It doesn't cover
binary installations via pkg_install.
I think Doug and Phillip were on the right track with pushing the data
into a pkg_install consumable format, but the only problem is that
creating additional code that handles one more corner case for
@comment will serve to only slow down the plist parser unnecessarily.
That's why I was suggesting a scripting infrastructure, like so:
pkgmsg() {
local message=$1
pkgmsg_separator
echo $message
pkgmsg_separator
}
Example:
echo This is an install message for my awesome new package
foo-BLAH +DISPLAY
pkgmsg `cat +DISPLAY`
And considering that you almost get the functionality for free via
pkg_install (from pkg_create(8)):
-D displayfile
Display the file (by concatenating it to stdout) after installing
the package. Useful for things like legal notices on almost-free
software, etc.
The thing about using a script function like pkgmsg too is that it can
be dynamically overwritten by certain groups in order to tailor the
messages (or mute output for customer purposes after everything has
passed QA if they use pkg_install in a product) to the meet their
needs when doing localized installations or deployments as well.
So, why not just add the relevant bits as I described?
Thanks,
-Garrett
___
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
graphics/libchamplain python bindings failure
Good day! Can please anybody, who have graphics/libchamplain installed, confirm this: [...@smeshariki2 ~] python -c import champlain Traceback (most recent call last): File string, line 1, in module ImportError: /usr/local/lib/python2.6/site-packages/champlain.so: Undefined symbol champlain_functions I'm using 0.4.6 from ports on 8-stable. Thanks in advance. PS. I'm opened this bug in libchamplain's bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=622232 but the guys told me that all is ok for them. I just want to understand where is the problem: a) on my local machine b) in FreeBSD port c) in libchamplain -- Regards, Ruslan ___ 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
buildbot test failure on freebsd 8.0-stable
where do i report buildbot test failures? and how can i tell if it is
fatal?
randy
% uname -a
FreeBSD work0.psg.com 8.0-STABLE FreeBSD 8.0-STABLE #8: Fri Mar 12 02:40:52 UTC
2010 r...@work0.psg.com:/usr/obj/usr/src/sys/WORK0 amd64
--- START step svn / log stdio ---
starting svn operation
rm -rf /usr/home/buildbot/_trial_temp/slavebase/vc-dir/build
in dir /usr/home/buildbot/_trial_temp/slavebase/vc-dir (timeout 200 secs)
watching logfiles {}
argv: ['rm', '-rf', '/usr/home/buildbot/_trial_temp/slavebase/vc-dir/build']
environment:
BLOCKSIZE=K
EDITOR=vi
ENV=/usr/home/buildbot/.shrc
EXINIT=set sh=/bin/csh sw=4 ai report=2
EXRC=/usr/home/buildbot/.exrc
FTP_PASSIVE_MODE=YES
HISTFILESIZE=50
HISTIGNORE=
HISTSIZE=500
HOME=/usr/home/buildbot
LD_TCL_TK_LIBS=-ltk42 -ltcl76
LESS=-aCeiM -P %i/%m %f %lt/%L %pb\%
LOGNAME=buildbot
MAIL=/var/mail/buildbot
MANPATH=/usr/share/man:/usr/share/perl/man:/usr/local/man:/usr/X11R6/man:/usr/share/openssl/man
PAGER=more
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/home/buildbot/bin
PWD=/usr/home/buildbot/_trial_temp/slavebase/vc-dir
PYTHONPATH=.
SHELL=/usr/local/bin/bash
SHLVL=1
SSH_AUTH_SOCK=/tmp/ssh-322WjekvPv/agent.83413
SSH_CLIENT=210.138.216.50 52705 22
SSH_CONNECTION=210.138.216.50 52705 147.28.0.35 22
SSH_TTY=/dev/pts/5
TCL_LIBRARY=/usr/local/lib:/usr/local/lib/tcl7.6
TCL_TK_INCLUDE_DIR=/usr/local/include/tcl7.6:/usr/local/include/tk4.2
TCL_TK_LIBRARY_DIR=/usr/local/lib
TERM=xterm
TK_LIBRARY=/usr/local/lib:/usr/local/lib/tk4.2
USER=buildbot
VISUAL=/usr/local/bin/emacs
_=/usr/local/bin/trial
closing stdin
using PTY: False
rm: /usr/home/buildbot/_trial_temp/slavebase/vc-dir/build/subdir: Permission
denied
rm: /usr/home/buildbot/_trial_temp/slavebase/vc-dir/build: Directory not empty
elapsedTime=0.085451
chmod -R u+rwx /usr/home/buildbot/_trial_temp/slavebase/vc-dir/build
in dir /usr/home/buildbot/_trial_temp/slavebase/vc-dir (timeout 200 secs)
watching logfiles {}
argv: ['chmod', '-R', 'u+rwx',
'/usr/home/buildbot/_trial_temp/slavebase/vc-dir/build']
environment:
BLOCKSIZE=K
EDITOR=vi
ENV=/usr/home/buildbot/.shrc
EXINIT=set sh=/bin/csh sw=4 ai report=2
EXRC=/usr/home/buildbot/.exrc
FTP_PASSIVE_MODE=YES
HISTFILESIZE=50
HISTIGNORE=
HISTSIZE=500
HOME=/usr/home/buildbot
LD_TCL_TK_LIBS=-ltk42 -ltcl76
LESS=-aCeiM -P %i/%m %f %lt/%L %pb\%
LOGNAME=buildbot
MAIL=/var/mail/buildbot
MANPATH=/usr/share/man:/usr/share/perl/man:/usr/local/man:/usr/X11R6/man:/usr/share/openssl/man
PAGER=more
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/home/buildbot/bin
PWD=/usr/home/buildbot/_trial_temp/slavebase/vc-dir
PYTHONPATH=.
SHELL=/usr/local/bin/bash
SHLVL=1
SSH_AUTH_SOCK=/tmp/ssh-322WjekvPv/agent.83413
SSH_CLIENT=210.138.216.50 52705 22
SSH_CONNECTION=210.138.216.50 52705 147.28.0.35 22
SSH_TTY=/dev/pts/5
TCL_LIBRARY=/usr/local/lib:/usr/local/lib/tcl7.6
TCL_TK_INCLUDE_DIR=/usr/local/include/tcl7.6:/usr/local/include/tk4.2
TCL_TK_LIBRARY_DIR=/usr/local/lib
TERM=xterm
TK_LIBRARY=/usr/local/lib:/usr/local/lib/tk4.2
USER=buildbot
VISUAL=/usr/local/bin/emacs
_=/usr/local/bin/trial
closing stdin
using PTY: False
chmod: /usr/home/buildbot/_trial_temp/slavebase/vc-dir/build/subdir: Permission
denied
elapsedTime=0.089292
program finished with exit code 1
--- STOP ---
[FAIL]
testCheckoutBranch ... [OK]
testPatch ... [OK]
testPatchP2 ...[OK]
testPatchSubDir ...[OK]
testTry ...[OK]
Sources
testCVS1 ... [OK]
testCVS2 ... [OK]
testCVS3 ... [OK]
testCVS4 ... [OK]
testSVN1 ... [OK]
testSVN2 ... [OK]
buildbot.test.test_web
GetURL
testBase ... [OK]
testBuild ... [OK]
testChange ... [OK]
testMissingBase ...[OK]
Logfile
test_logfile1 ... [OK]
test_logfile2 ... [OK]
test_logfile3 ...
Re: Call for testers: www/shellinabox (Shell in a Box)
2010/6/24 Olivier Cochard-Labbé oliv...@freenas.org: I've just finished my port of Shell in a Box: It's a secure web server that provide ajax terminal emulator. More information on the official website: http://code.google.com/p/shellinabox/ I'll test it! I've actually had written on my daily todo list port for shellinabox, and I haven't gotten around to it. I'll let you know what I find out. -- Christer Edwards ___ 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: Call for testers: www/shellinabox (Shell in a Box)
On Fri 2010-06-25 00:51:12 UTC+0200, Olivier Cochard-Labb? (oliv...@freenas.org) wrote: I've just finished my port of Shell in a Box: It's a secure web server that provide ajax terminal emulator. Very cool :-) More information on the official website: http://code.google.com/p/shellinabox/ Your port builds OK and seems to run fine here under FreeBSD 7.3-RELEASE. Thanks Olivier. ___ 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: Call for testers: www/shellinabox (Shell in a Box)
On 6/24/10 6:51 PM, Olivier Cochard-Labbé wrote: Hi all, I've just finished my port of Shell in a Box: It's a secure web server that provide ajax terminal emulator. More information on the official website: http://code.google.com/p/shellinabox/ Before to submit it, Can someone test it ? You can found the port here: http://gugus69.free.fr/tools/shellinabox.tgz Here is how to proceed: cd /usr/ports/www fetch http://gugus69.free.fr/tools/shellinabox.tgz tar zxvf shellinabox.tgz cd shellinabox make install clean /usr/local/etc/rc.d/shellinaboxd onestart Then start your browser and connect to: https://127.0.0.1:4200 Cool stuff. Builds/runs fine on: FreeBSD orion 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #2 r209399: Mon Jun 21 20:36:54 EDT 2010 r...@orion:/usr/obj/usr/src/sys/ORION amd64 Safari doesn't play nice with it, but neat little tool. -- Glen Barber ___ 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: Call for testers: www/shellinabox (Shell in a Box)
On 06/24/10 15:51, Olivier Cochard-Labbé wrote:
Hi all,
I've just finished my port of Shell in a Box: It's a secure web server
that provide ajax terminal emulator.
More information on the official website:
http://code.google.com/p/shellinabox/
Before to submit it, Can someone test it ?
You can found the port here: http://gugus69.free.fr/tools/shellinabox.tgz
I didn't test the port, but attached is a diff to your rc.d script. For
more information take a look at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html
Some notes:
1. We like to have a $FreeBSD id line in rc.d scripts
2. We support case sensitivity for arguments like your _fib option, so
case is a better choice here.
3. You need a default for _enable. To see why, comment out the entry you
have in /etc/rc.conf[.local] and then try running the script.
4. There is no need for a custom start_cmd here, and it's better to take
advantage of the rc.d infrastructure (that includes fixing your typo for
pidfile).
5. I added the required_dirs since it seems like that's mandatory.
6. By convention the argument for backgrounding the daemon is the last
one listed, but that's just a style nit.
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/
--- shellinaboxd.in.orig2010-06-24 15:44:16.0 -0700
+++ shellinaboxd.in 2010-06-24 19:02:03.0 -0700
@@ -1,4 +1,6 @@
#!/bin/sh
+
+# $FreeBSD$
#
# Shell in a Box Daemon startup script
#
@@ -20,11 +22,14 @@
shellinaboxd_setfib() {
sysctl net.fibs /dev/null 21 || return 0
- if [ x${shellinaboxd_fib} != xNONE ]; then
+
+ case $shellinaboxd_fib in
+ [Nn][Oo][Nn][Ee])
+ ;;
+ *)
command=setfib -F ${shellinaboxd_fib} ${command}
- else
- return 0
- fi
+ ;;
+ esac
}
. /etc/rc.subr
@@ -36,13 +41,16 @@
start_precmd=shellinaboxd_setfib
load_rc_config $name
+
+shellinaboxd_enable=${shellinaboxd_enable:-NO}
shellinaboxd_fib=${shellinaboxd_fib:-NONE}
-shellinaboxd_pidfile=${shellinaboxd_pidfile:-/var/run/shellinaboxd.pid}
shellinaboxd_port=${shellinaboxd_port:-4200}
shellinaboxd_certdir=${shellinaboxd_certdir:-%%PREFIX%%/etc/shellinabox}
-start_cmd=$command --port=${shellinaboxd_port}
--background=${shellinaboxd_pidfile} --cert=${shellinaboxd_certdir}
+pidfile=${shellinaboxd_pidfile:-/var/run/shellinaboxd.pid}
+
+required_dirs=${shellinaboxd_certdir}
-pid_file=${shellinaboxd_pidfile}
+command_args=--port=${shellinaboxd_port} --cert=${shellinaboxd_certdir}
--background=${pidfile}
run_rc_command $1
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
