Quick status update on Squid 3.x ports
Hi, this is just a short update on the status of Squid 3 ports. As you may have noticed I am a bit behind with regards to Squid 3.2. Sorry for that -- I could not spend much time for ports development in the last few months. To add insult to injury I will be offline for the next couple of days but I plan to have the 3.2 port ready in the week starting Oct 7 nonetheless. I just submitted an update request for 3.1 to 3.1.21 for the time being. On a side note: in the past, the default Squid port was named www/squid and the older or development Squid versions had versioned port directory names. Should we move www/squid to www/squid27 instead and make all Squid dependend ports that currently depend on www/squid use www/squid27 instead? Best regards -- Thomas-Martin Seck pgpVD4BZTTArF.pgp Description: PGP signature
Re: CFT: x11/nvidia-driver major update to 304.xx series
On Wed, Sep 26, 2012 at 03:35:07PM -0400, Lawrence K. Chen, P.Eng. wrote: > So, now that its in the wild...I upgraded...and it broke my dual monitor > desktop (at work). Seems like gdm/gnome can't see the other monitor.] > Tried rebuilding a bunch of other things, but didn't help. Reverting to > previous (295.71) has things working again. Wonder what people will do > for portdowngrade when CVS goes away. No need for portdowngrade actually, you can always build the port against DISTVERSION of your choice, by doing: make DISTVERSION=xxx.yy -DNO_CHECKSUM This works most of the time since pkg-plist changes rarely, so it would even give you nice valid package. Perhaps you could try new version, 304.51, this way and report us back if it fixes things for you? ./danfe ___ 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: security/sudo: make fails after update to 1.8.6p3
From: Wesley Shields Subject: Re: security/sudo: make fails after update to 1.8.6p3 Date: Wed, 26 Sep 2012 17:00:09 -0400 > This patch [1] should suffice. Please test it out and let me know. > > [1]: http://people.freebsd.org/~wxs/sudo-ssp.diff It works fine for me. Thank you. --- Yasuhiro KIMURA ___ 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: [PATCH] unbreak imake build when clang set as base compiler
On 9/27/12, Oliver Pinter wrote: > On 9/26/12, Garrett Cooper wrote: >> On Wed, Sep 26, 2012 at 2:18 PM, Oliver Pinter >> wrote: >>> On 9/26/12, Garrett Cooper wrote: On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter wrote: > Hi all! > > This patch fixed the problem, when buildig imake on a machine where > clang is the base the compiler (WITH_CLANG_IS_CC). (Picking a random message to reply to) Why not create PRs and CC the relevant parties? >>> >>> because I hope, there become this issue a mote attention ;) >> >> Or gets lost in someone's mailbox :(... >> >>> of course, I create in near future a PR, but before that, I send an >>> updated patch, and yes, I know, that this is not a clean solution, but >>> better than nothing. >> >> Having a PR is better than a random email that will most likely get >> lost. I would definitely respond to: >> >> "Hey $dev! I filed $PR -- can you please take a look at it? It solves >> '$reason'. Thanks!" > > ports/172103 ports/172104 ports/172102 ports/172101 ports/172100 ;) and the patches are here too: http://oliverp.teteny.bme.hu/freebsd/patches/ports-clang/ > >> >> You might get better results this way too and less duplicated effort >> by multiple individuals.. just sayin'... >> >> 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"
Re: [PATCH] unbreak imake build when clang set as base compiler
On 9/26/12, Garrett Cooper wrote: > On Wed, Sep 26, 2012 at 2:18 PM, Oliver Pinter > wrote: >> On 9/26/12, Garrett Cooper wrote: >>> On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter >>> wrote: Hi all! This patch fixed the problem, when buildig imake on a machine where clang is the base the compiler (WITH_CLANG_IS_CC). >>> >>> (Picking a random message to reply to) Why not create PRs and CC the >>> relevant parties? >> >> because I hope, there become this issue a mote attention ;) > > Or gets lost in someone's mailbox :(... > >> of course, I create in near future a PR, but before that, I send an >> updated patch, and yes, I know, that this is not a clean solution, but >> better than nothing. > > Having a PR is better than a random email that will most likely get > lost. I would definitely respond to: > > "Hey $dev! I filed $PR -- can you please take a look at it? It solves > '$reason'. Thanks!" ports/172103 ports/172104 ports/172102 ports/172101 ports/172100 ;) > > You might get better results this way too and less duplicated effort > by multiple individuals.. just sayin'... > > 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"
Re: [PATCH] unbreak imake build when clang set as base compiler
On Wed, Sep 26, 2012 at 2:18 PM, Oliver Pinter wrote: > On 9/26/12, Garrett Cooper wrote: >> On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter >> wrote: >>> Hi all! >>> >>> This patch fixed the problem, when buildig imake on a machine where >>> clang is the base the compiler (WITH_CLANG_IS_CC). >> >> (Picking a random message to reply to) Why not create PRs and CC the >> relevant parties? > > because I hope, there become this issue a mote attention ;) Or gets lost in someone's mailbox :(... > of course, I create in near future a PR, but before that, I send an > updated patch, and yes, I know, that this is not a clean solution, but > better than nothing. Having a PR is better than a random email that will most likely get lost. I would definitely respond to: "Hey $dev! I filed $PR -- can you please take a look at it? It solves '$reason'. Thanks!" You might get better results this way too and less duplicated effort by multiple individuals.. just sayin'... 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"
Re: [PATCH] unbreak imake build when clang set as base compiler
On 9/26/12, Garrett Cooper wrote: > On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter > wrote: >> Hi all! >> >> This patch fixed the problem, when buildig imake on a machine where >> clang is the base the compiler (WITH_CLANG_IS_CC). > > (Picking a random message to reply to) Why not create PRs and CC the > relevant parties? because I hope, there become this issue a mote attention ;) of course, I create in near future a PR, but before that, I send an updated patch, and yes, I know, that this is not a clean solution, but better than nothing. > ___ 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: Failed upgrade sudo-1.8.5.p3 to sudo-1.8.6.p3 running stable/9
On Wed, Sep 26, 2012 at 04:59:28PM -0400, Wesley Shields wrote: > On Wed, Sep 26, 2012 at 04:43:57AM -0700, David Wolfskill wrote: > > This is a FreeBSD/i386 stable/9 system: > > > > FreeBSD freebeast.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #485 > > 240956M: Wed Sep 26 04:19:48 PDT 2012 > > r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 > > > > built with clang, but cc is gcc: > > This is a failure on i386 only, which is why I didn't notice it. Would > you apply the patch available at [1] and let me know if it works. It > does build for me now that I built up a i386 environment. > > [1]: http://people.freebsd.org/~wxs/sudo-ssp.diff > Aye; builds & a trivial test: d134(9.1-P)[1] sudo id Password: uid=0(root) gid=0(wheel) groups=0(wheel),5(operator) d134(9.1-P)[2] works. :-} Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpuQGd0sT9XV.pgp Description: PGP signature
Re: security/sudo: make fails after update to 1.8.6p3
On Wed, Sep 26, 2012 at 09:43:06PM +0900, Yasuhiro KIMURA wrote: > From: ??ukasz W??sikowski > Subject: Re: security/sudo: make fails after update to 1.8.6p3 > Date: Wed, 26 Sep 2012 14:14:37 +0200 > > > W dniu 2012-09-26 13:57, Herbert J. Skuhra pisze: > > > >>> After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as > >>> following: > >>> > >>> [Several lines removed] > >>> > >>> Are there anyone alse experienced this? > >> > >> Yes, the port obviously builds only on amd64. > > > > True, I've installed it successfully on amd64 and got the same error on > > i386 box. > > Thanks. I found PR for this issue is already sent. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/172085 > > So I'll wait for maintainer's reaction. This patch [1] should suffice. Please test it out and let me know. [1]: http://people.freebsd.org/~wxs/sudo-ssp.diff -- 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: Failed upgrade sudo-1.8.5.p3 to sudo-1.8.6.p3 running stable/9
On Wed, Sep 26, 2012 at 04:43:57AM -0700, David Wolfskill wrote: > This is a FreeBSD/i386 stable/9 system: > > FreeBSD freebeast.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #485 > 240956M: Wed Sep 26 04:19:48 PDT 2012 > r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC i386 > > built with clang, but cc is gcc: This is a failure on i386 only, which is why I didn't notice it. Would you apply the patch available at [1] and let me know if it works. It does build for me now that I built up a i386 environment. [1]: http://people.freebsd.org/~wxs/sudo-ssp.diff -- 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"
FreeBSD Port: fusefs-encfs-1.7.4_1
Hello; I have been using encfs successfully for many months. % encfs ~/.crypt ~/files/crypt Today, I tried to mount the same way as usual. My password was accepted, but the directory ~/files/crypt disappeared after the mount. That is, before the command above I see the ~/files/crypt directory, but after it doesn't show up with an ls -la. However, when I do ls ~/files/crypt I see the message "ls: crypt: Bad file descriptor". The ~/.crypt directory seems unchanged. The only thing I can think of that might have changed in the past few days: I may have updated a dependent port (e.g. /deve/icu). I'm running 9-STABLE amd64 with port version 1.7.4_1. Thanks for any suggestions. Joseph ___ 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: CFT: x11/nvidia-driver major update to 304.xx series
So, now that its in the wild...I upgraded...and it broke my dual monitor desktop (at work). Seems like gdm/gnome can't see the other monitor. Tried rebuilding a bunch of other things, but didn't help. Reverting to previous (295.71) has things working again. Wonder what people will do for portdowngrade when CVS goes away. OTOH, I upgraded my system at home, and the desktop is still working fine. It says it still supports my graphics cardthough. At work I have a Quadro FX 1400 driving a pair of 1600x1200 monitors. At home I have a Quadro FX 1700 driving a pair of 1920x1080 monitors. - Original Message - > On Wed, Sep 19, 2012 at 11:55 AM, Alexey Dokuchaev > wrote: > > As many of you had probably noticed, recently folks at NVidia > > decided that > > long-cooked three-hundred branch is stable enough to declare it > > Long Lived > > Branch. Since ChangeLog from 295.71/.75 is gross, and I've been > > receiving > > mixed reviews for early 30x.?? versions, I am calling for testers > > to help > > me make weighted decision about updating the port to 304.43. If, > > for some > > reason, 304.43 does not work for you, tell me how does version > > 295.75 feel > > (just do "make DISTVERSION=304.43 or 295.75 -DNO_CHECKSUM install" > > to test > > it out, pkg-plist is the same as current one). > > After a couple of days of usage everything keeps working as usual; I > see absolutely no difference from old version. > > nvidia0: on vgapci0 > -- > Alberto Villa, FreeBSD committer > http://people.FreeBSD.org/~avilla > ___ > 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" > -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library ___ 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"
aspell conflicts with ispell?
When did this happen? I have numerous packages that depend on ispell and numerous packages that depend on aspell. And, a bunch that depend on both. And, they are both installed currently. -- Who: Lawrence K. Chen, P.Eng. - W0LKC - Senior Unix Systems Administrator For: Enterprise Server Technologies (EST) -- & SafeZone Ally Snail: Computing and Telecommunications Services (CTS) Kansas State University, 109 East Stadium, Manhattan, KS 66506-3102 Phone: (785) 532-4916 - Fax: (785) 532-3515 - Email: lkc...@ksu.edu Web: http://www-personal.ksu.edu/~lkchen - Where: 11 Hale Library ___ 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"
mailman upgrade bug
The mailman-2.1.14_6 port appears to be broken. After cvsup, whether reinstalling or installing from scratch, several essential files and directories are not installed. admin(26870): [- Mailman Version: 2.1.14 -] admin(26870): [- Traceback --] admin(26870): Traceback (most recent call last): admin(26870): File "/usr/local/mailman/scripts/driver", line 112, in run_main admin(26870): main() admin(26870): File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 112, in main admin(26870): Auth.loginpage(mlist, 'admindb', msg=msg) admin(26870): File "/usr/local/mailman/Mailman/Cgi/Auth.py", line 60, in loginpage admin(26870): }, mlist=mlist) admin(26870): File "/usr/local/mailman/Mailman/Utils.py", line 580, in maketext admin(26870): return findtext(templatefile, dict, raw, lang, mlist)[0] admin(26870): File "/usr/local/mailman/Mailman/Utils.py", line 557, in findtext admin(26870): raise IOError(errno.ENOENT, 'No template file found', templatefile) admin(26870): IOError: [Errno 2] No template file found: 'admlogin.html' admin(26870): [- Python Information -] admin(26870): sys.version = 2.6.8 (unknown, May 3 2012, 08:38:55) [GCC 4.2.1 20070719 [FreeBSD]] admin(26870): sys.executable = /usr/local/bin/python2.6 admin(26870): sys.prefix = /usr/local admin(26870): sys.exec_prefix = /usr/local admin(26870): sys.path= ['/usr/local/mailman/pythonlib', '/usr/local/mailman', '/usr/local/mailman/scripts', '/usr/local/mailman', '/usr/local/lib/python26.zip', '/usr/local/lib/python2.6/', '/usr/local/lib/python2.6/plat-freebsd8', '/usr/local/lib/python2.6/lib-tk', '/usr/local/lib/python2.6/lib-old', '/usr/local/lib/python2.6/lib-dynload', '/usr/local/lib/python2.6/site-packages'] admin(26870): sys.platform= freebsd8 Roger Marquis ___ 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/mapserver] PHP Mapscript
Hi,
I have a problem with PHP Mapscript (the graphics/mapserver package). I
suppose the problem is in conjunction with the combination of lang/php5
(PHP 5.4.6) and Mapserver 6.0.3. Everytime I try to initiate a new
mapObj in mapscript, PHP segfaults.
My testscript:
ms_GetVersion() still works, but the next line ($map = new
mapObj('test.map')) causes the segmentation fault to happen:
brfr@frodo# php -f pi.php
MapServer version 6.0.3 OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG SUPPORTS=PROJ
SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER
SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
SUPPORTS=GEOS INPUT=POSTGIS INPUT=OGR INPUT=GDAL
INPUT=SHAPEFILESegmentation fault (core dumped)
An examination of the core with gdb yields
brfr@frodo# gdb /usr/local/bin/php php.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Core was generated by `php'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libcrypt.so.5...done.
Loaded symbols for /lib/libcrypt.so.5
[snip ...]
Reading symbols from /usr/local/lib/php/20100525-debug/tidy.so...done.
Loaded symbols for /usr/local/lib/php/20100525-debug/tidy.so
Reading symbols from /usr/local/lib/libtidy-0.99.so.0...done.
Loaded symbols for /usr/local/lib/libtidy-0.99.so.0
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x0069a10a in zend_std_get_constructor (object=0x8024762c8)
at /usr/ports/lang/php5/work/php-5.4.6/Zend/zend_object_handlers.c:1271
1271 /usr/ports/lang/php5/work/php-5.4.6/Zend/zend_object_handlers.c: No
such file or directory.
in /usr/ports/lang/php5/work/php-5.4.6/Zend/zend_object_handlers.c
[New Thread 802407400 (LWP 100919/php)]
(gdb)
I tried compiling everything back and forth, enabled and disabled all
kinds of PHP extensions but nothing helps. Segfault is coming always
back to me. Btw.
root@frodo# php -v
PHP 5.4.6 (cli) (built: Sep 26 2012 15:32:23) (DEBUG)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
works, and all non-mapscript PHP applications seem to run fine.
So, finally, any tipps to solve this problem are greatly appreceated ...
Frank
--
Frank BRONIEWSKI
METRICO s.à r.l.
géomètres
technologies d'information géographique
rue des Romains 36
L-5433 NIEDERDONVEN
tél.: +352 26 74 94 - 28
fax.: +352 26 74 94 99
http://www.metrico.lu
___
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: do I need to specify explicity what to install for make install to work?
From m.sea...@infracaninophile.co.uk Wed Sep 26 14:21:51 2012 On 26/09/2012 13:06, Anton Shterenlikht wrote: > I was updating my port until I got to > > make: don't know how to make install. Stop > *** [do-install] Error code 2 > > and I realised that I don't really understand > the sequence of commands involved in "make install". > I've looked through the porter's handbook, > but still not clear. > > I see lots of post-install targets in > Makefiles, but never just "install". > I presume it should be pulled into by > .include > > Still, if I have a set of source files, > generated object files, and just one > executable I want to install, I probably > have to specify somewhere in the Makefile > the name of this executable, right? > > Or are PLIST_FILES and PLIST_DIRS used > to let make know what to install? The ports 'make install' generally does one of two things: either it runs appropriate make install commands from $WRKDIR -- ie. what the ported software provides itself -- or it has a list of files, directories etc. from within $WRKDIR which it copies into place itself, which is usually only done if the ported software doesn't provide its own installation routines. As I recall, if you don't provide an explicit install target yourself, the default is to run 'make install' from $WRKDIR. PLIST_FILES, PLIST_DOCS or the pkg-plist file don't tell the ports what to install. Instead, they document what the installation process should be installing, and so what files to include in a pkg tarball and what to delete at pkg deinstallation time. Hence the effort required to make sure your plist is accurate. Ok, I think I get it. All I need is the install target in $WRKDIR/Makefile. If I make this target empty, then I can add the real install commands under post-install in the port's Makefile. However, it seems if there is no install target in $WRKDIR/Makefile, then I must add install target to port's Makefile. Anton Cheers, Matthew ___ 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: x11/Terminal - why not xfce4-terminal
2012/9/26 Florent Peterschmitt : > Le 26/09/2012 12:26, Sergey V. Dyatko a écrit : > >> On Wed, 26 Sep 2012 14:17:57 + >> Florent Peterschmitt wrote: >> >>> Hello, >>> >>> Why the terminal emulator from XFCE4 is called Terminal instead of >>> xfce4-terminal ? >> >> http://goodies.xfce.org/projects/applications/terminal >> >> >> > Ok, then next question. Why xfce apps are not under un sub-directory called > xfce (or xfce4 if versionning becomes important) ? > What do you mean by « Why xfce apps are not under un sub-directory called xfce » ? -- 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: do I need to specify explicity what to install for make install to work?
From m.sea...@infracaninophile.co.uk Wed Sep 26 14:21:51 2012
On 26/09/2012 13:06, Anton Shterenlikht wrote:
> I was updating my port until I got to
>
> make: don't know how to make install. Stop
> *** [do-install] Error code 2
>
> and I realised that I don't really understand
> the sequence of commands involved in "make install".
> I've looked through the porter's handbook,
> but still not clear.
>
> I see lots of post-install targets in
> Makefiles, but never just "install".
> I presume it should be pulled into by
> .include
>
> Still, if I have a set of source files,
> generated object files, and just one
> executable I want to install, I probably
> have to specify somewhere in the Makefile
> the name of this executable, right?
>
> Or are PLIST_FILES and PLIST_DIRS used > to let make know what to
install?
The ports 'make install' generally does one of two things: either it
runs appropriate make install commands from $WRKDIR -- ie. what the
ported software provides itself -- or it has a list of files,
directories etc. from within $WRKDIR which it copies into place itself,
How do I specify this list?
which is usually only done if the ported software doesn't provide its
own installation routines. As I recall, if you don't provide an
explicit install target yourself, the default is to run 'make install'
from $WRKDIR.
PLIST_FILES, PLIST_DOCS or the pkg-plist file don't tell the ports what
to install. Instead, they document what the installation process should
be installing, and so what files to include in a pkg tarball and what to
delete at pkg deinstallation time. Hence the effort required to make
sure your plist is accurate.
Ok, I have in my port, astro/xearth
(inherited when I took over the maintainership):
post-install:
@${INSTALL_MAN} ${WRKSRC}/xearth.man ${MANPREFIX}/man/man1/xearth.1
@${MKDIR} ${PREFIX}/lib/X11/xearth
# Copy the list of FreeBSD sites & committers locations
.for marker in freebsd.committers.markers freebsd.submitters.markers
freebsd.ftp.markers
@${INSTALL_DATA} ${FILESDIR}/${marker} ${PREFIX}/lib/X11/xearth
.endfor
So, looking at this, the xearth binary
is installed by running "make install"
from under $WRKDIR.
Then post-install installs the man page,
creates the directory to hold a few
extra files, and copies the files there.
I'm thinking about having all install
related commands in one place. So is
it a good idea to move all post-install
commands as a part of the software's
own Makefile install target?
Or alternatively, I'd like to move
the installation of the binary to
the port's Makefile, just not sure
where and how to specify it.
Presumably this should come instead
of post-install?
Thanks
Anton
___
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: emacs23
On 09/23/12 00:21, Ashish SHUKLA wrote: Hi Andrea, I don't use GDB integration of Emacs to notice any breakage. Could you post here (or on emacs-devel[1] list) about problems you're facing, and if reproducible by others as well, then we can probably file a bug report on Emacs bug tracker[2]. I'll post here, since I don't know whether this is a FreeBSD specific problem. The box is running 8.3/i386 (but on 9.0 it's the same). The problem is quite complex, meaning so many things are just screwed up that you end up wondering if this is production ready software. I'll try to explain with an example session, which I hope will show some of the bugs of the new version; I'm open to feedback in case something is not clear. %emacs & M-x gdb (I'm prompted with "gdb -i=mi" and just add the executable name). (I get "This version of GDB doesn't support non-stop mode. Turnig it off"; I don't know what this means, I just ignore it.) b main r (I get argc=Error accessing memory address 0x0: Bad address.) p argc (I get Error accessing memory address 0x0: Bad address.) (Ok, so I cannot look into a variable). frame (I'd expect to see the source, but I don't). C-x C-f and I open the source manually. (Positioned on the source line I want a breakpoint on) C-x Space (The dot appears grey, not red, as tough the source was not recognized; however the breakpoint seems to work). r (The program starts and stops at the first breakpoint; however I get no indication of this in the source window). n (Nothing happens, the pointer in the source does not move, in *gud* windows the same line is reported) n (Nothing happens, the pointer in the source does not move, in *gud* windows the same line is reported) n (Debugger segmentation fault: 11 (core dumped)) Ok, I give up with gdb from base and try gdb75 from ports. M-x gdb (I'm prompted with "gdb -i=mi", add the executable name and substitute "gdb" with "/usr/local/bin/gdb75"). b main r n (Things work better here; I get an *input/output* windows I cannot get rid of) c After a while C-c C-c (The program stops in "write" from the runtime outside my program) frame (gdb locks up) %kill gdb75 M-x gdb "The program is already being debugged" C-x C-k M-x gdb (I'm prompted with "gdb -i=mi", add the executable name and substitute "gdb" with "/usr/local/bin/gdb75"). (Ok this time) r After a while C-c C-c (The program stops in "read" from the runtime outside my program) (avoiding the use of "frame", which produced a lockup earlier) bt frame 7 (now in my program) I move to the next line and give C-x Space (nothing happens; from now on I cannot insert breakpoints this way) b foo.cxx:45 (manual insert of breakpoint works) fin fin fin fin fin fin n (program moves correctly to the next line) (I lose "(gdb)" prompt, so I have an hard time trying to tell what I wrote from what the debugger wrote; also if I leave the window for a while, when I'm back I have to guess whether the program is running or stopped) b 'funcThis is of course only an example, but it shows most of the ways in which I found emacs24+gdb can fail or annoy. I suspect there are others. Since it cannot be pinpointed to a single bug, I guess either some version incompatibility or some wrong compilation option, but I really don't know where to look. And, as for the security vulnerability which I forgot to fix for editors/emacs23 (my fault, apologies), I'm testing a fix[3] in tinderbox, once it builds fine, I'll commit it. Thanks for this. bye av. ___ 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: security/sudo: make fails after update to 1.8.6p3
From: Łukasz Wąsikowski Subject: Re: security/sudo: make fails after update to 1.8.6p3 Date: Wed, 26 Sep 2012 14:14:37 +0200 > W dniu 2012-09-26 13:57, Herbert J. Skuhra pisze: > >>> After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as >>> following: >>> >>> [Several lines removed] >>> >>> Are there anyone alse experienced this? >> >> Yes, the port obviously builds only on amd64. > > True, I've installed it successfully on amd64 and got the same error on > i386 box. Thanks. I found PR for this issue is already sent. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/172085 So I'll wait for maintainer's reaction. --- Yasuhiro KIMURA ___ 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: x11/Terminal - why not xfce4-terminal
Le 26/09/2012 12:26, Sergey V. Dyatko a écrit : On Wed, 26 Sep 2012 14:17:57 + Florent Peterschmitt wrote: Hello, Why the terminal emulator from XFCE4 is called Terminal instead of xfce4-terminal ? http://goodies.xfce.org/projects/applications/terminal Ok, then next question. Why xfce apps are not under un sub-directory called xfce (or xfce4 if versionning becomes important) ? ___ 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: x11/Terminal - why not xfce4-terminal
On Wed, 26 Sep 2012 14:17:57 + Florent Peterschmitt wrote: > Hello, > > Why the terminal emulator from XFCE4 is called Terminal instead of > xfce4-terminal ? http://goodies.xfce.org/projects/applications/terminal -- wbr, tiger ___ 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: do I need to specify explicity what to install for make install to work?
On 26/09/2012 13:06, Anton Shterenlikht wrote: > I was updating my port until I got to > > make: don't know how to make install. Stop > *** [do-install] Error code 2 > > and I realised that I don't really understand > the sequence of commands involved in "make install". > I've looked through the porter's handbook, > but still not clear. > > I see lots of post-install targets in > Makefiles, but never just "install". > I presume it should be pulled into by > .include > > Still, if I have a set of source files, > generated object files, and just one > executable I want to install, I probably > have to specify somewhere in the Makefile > the name of this executable, right? > > Or are PLIST_FILES and PLIST_DIRS used > to let make know what to install? The ports 'make install' generally does one of two things: either it runs appropriate make install commands from $WRKDIR -- ie. what the ported software provides itself -- or it has a list of files, directories etc. from within $WRKDIR which it copies into place itself, which is usually only done if the ported software doesn't provide its own installation routines. As I recall, if you don't provide an explicit install target yourself, the default is to run 'make install' from $WRKDIR. PLIST_FILES, PLIST_DOCS or the pkg-plist file don't tell the ports what to install. Instead, they document what the installation process should be installing, and so what files to include in a pkg tarball and what to delete at pkg deinstallation time. Hence the effort required to make sure your plist is accurate. Cheers, Matthew ___ 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"
x11/Terminal - why not xfce4-terminal
Hello, Why the terminal emulator from XFCE4 is called Terminal instead of xfce4-terminal ? ___ 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: security/sudo: make fails after update to 1.8.6p3
W dniu 2012-09-26 13:57, Herbert J. Skuhra pisze: >> After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as >> following: >> >> [Several lines removed] >> >> Are there anyone alse experienced this? > > Yes, the port obviously builds only on amd64. True, I've installed it successfully on amd64 and got the same error on i386 box. -- best regards, Lukasz Wasikowski ___ 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"
do I need to specify explicity what to install for make install to work?
I was updating my port until I got to make: don't know how to make install. Stop *** [do-install] Error code 2 and I realised that I don't really understand the sequence of commands involved in "make install". I've looked through the porter's handbook, but still not clear. I see lots of post-install targets in Makefiles, but never just "install". I presume it should be pulled into by .include Still, if I have a set of source files, generated object files, and just one executable I want to install, I probably have to specify somewhere in the Makefile the name of this executable, right? Or are PLIST_FILES and PLIST_DIRS used to let make know what to install? Thanks Anton ___ 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: security/sudo: make fails after update to 1.8.6p3
On 26.09.2012 13:45, Yasuhiro KIMURA wrote: After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as following: [Several lines removed] Are there anyone alse experienced this? Yes, the port obviously builds only on amd64. -- Herbert ___ 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"
security/sudo: make fails after update to 1.8.6p3
After update of security/sudo to 1.8.6p3, make fails on 9.0-RELEASE as following: cc -c -I../../include -I../.. -I. -I. -I../.. -DLIBDIR=\"/usr/local/lib\" -O2 -pipe -I/usr/local/include -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fPIE -D_BSD_SOURCE -D_PATH_SUDOERS=\"/usr/local/etc/sudoers\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 -DLOCALEDIR=\"/usr/local/share/locale\" ./visudo.c cc -c -I../../include -I../.. -I. -I. -I../.. -DLIBDIR=\"/usr/local/lib\" -O2 -pipe -I/usr/local/include -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fPIE -D_BSD_SOURCE -D_PATH_SUDOERS=\"/usr/local/etc/sudoers\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 -DLOCALEDIR=\"/usr/local/share/locale\" ./getdate.c /bin/sh ../../libtool --mode=compile cc -c -I../../include -I../.. -I. -I. -I../.. -DLIBDIR=\"/usr/local/lib\" -O2 -pipe -I/usr/local/include -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fPIE -D_BSD_SOURCE -D_PATH_SUDOERS=\"/usr/local/etc/sudoers\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 -DLOCALEDIR=\"/usr/local/share/locale\" ./toke.c libtool: compile: cc -c -I../../include -I../.. -I. -I. -I../.. -DLIBDIR=\"/usr/local/lib\" -O2 -pipe -I/usr/local/include -fno-strict-aliasing -fvisibility=hidden -fstack-protector -D_BSD_SOURCE -D_PATH_SUDOERS=\"/usr/local/etc/sudoers\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 -DLOCALEDIR=\"/usr/local/share/locale\" ./toke.c -fPIC -DPIC -o .libs/toke.o /bin/sh ../../libtool --mode=link cc -o sudoreplay getdate.o sudoreplay.o error.o -lgcc -L/usr/local/lib -lintl -Wl,-z,relro -pie timestr.lo -lz ../../common/libcommon.la ../../compat/libreplace.la libtool: link: cc -o sudoreplay getdate.o sudoreplay.o error.o -Wl,-z -Wl,relro -pie .libs/timestr.o -lgcc -L/usr/local/lib /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -lz ../../common/.libs/libcommon.a ../../compat/.libs/libreplace.a -Wl,-rpath -Wl,/usr/local/lib -Wl,-rpath -Wl,/usr/local/lib getdate.o: In function `yylex': getdate.c:(.text+0x1eb): undefined reference to `__stack_chk_fail_local' sudoreplay.o: In function `.L120': sudoreplay.c:(.text+0xbc6): undefined reference to `__stack_chk_fail_local' sudoreplay.o: In function `find_sessions': sudoreplay.c:(.text+0x1874): undefined reference to `__stack_chk_fail_local' ../../common/.libs/libcommon.a(sudo_debug.o): In function `sudo_debug_write2': sudo_debug.c:(.text+0x450): undefined reference to `__stack_chk_fail_local' ../../common/.libs/libcommon.a(term.o): In function `term_copy': term.c:(.text+0x128): undefined reference to `__stack_chk_fail_local' ../../common/.libs/libcommon.a(term.o):term.c:(.text+0x569): more undefined references to `__stack_chk_fail_local' follow *** Error code 1 libtool: compile: cc -c -I../../include -I../.. -I. -I. -I../.. -DLIBDIR=\"/usr/local/lib\" -O2 -pipe -I/usr/local/include -fno-strict-aliasing -fvisibility=hidden -fstack-protector -D_BSD_SOURCE -D_PATH_SUDOERS=\"/usr/local/etc/sudoers\" -DSUDOERS_UID=0 -DSUDOERS_GID=0 -DSUDOERS_MODE=0440 -DLOCALEDIR=\"/usr/local/share/locale\" ./toke.c -fPIE -o toke.o >/dev/null 2>&1 1 error *** Error code 2 1 error *** Error code 1 Stop in /usr0/freebsd/ports/ports/security/sudo. *** Error code 1 Stop in /usr0/freebsd/ports/ports/security/sudo. Are there anyone alse experienced this? --- Yasuhiro KIMURA ___ 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: [BRAINSTORMIG] name of the variable for passing command line options via make
Olli Hauer ha scritto: >>> WITH / WITHOUT >> >> I thought this was a joke, but thinking about it, this is the best idea IMO. > > I agree, but silently thinking OH NO! this brings us back to the discussions > from a view months ago... > > If I understand correct the LATE_(UN)SET parameter can be used inside the port > after including bsd.port.options.mk (where I really miss it) and CMD_(UN)SET > from the command line. Hmm, no, I've understood that they are simply two different proposals for the same features, i.e. command line overriding. I vote for WITH / WITHOUT. -- Alex Dupre ___ 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: [PATCH] unbreak imake build when clang set as base compiler
On Wed, Sep 26, 2012 at 11:10:25AM +0200, Niclas Zeising wrote: > On 2012-09-26 01:13, Eitan Adler wrote: > > On 25 September 2012 18:45, Garrett Cooper wrote: > >> On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter > >> wrote: > >>> Hi all! > >>> > >>> This patch fixed the problem, when buildig imake on a machine where > >>> clang is the base the compiler (WITH_CLANG_IS_CC). > >> > >> (Picking a random message to reply to) Why not create PRs and CC the > >> relevant parties? > > The issue, as Jan pointed out in another thread, is that ucpp isn't > compatible with gnu cpp either. It causes other issues, the only > difference is that it passes the configure script test. > In my opinion, the solution to this problem is to fix the (X11) ports > that abuse cpp, and deprecate imake. This is not a solution as well. The imake is usable and used on its own for miriad of proprietary X/motif software. Removing it from ports is no-go. Not all useful software lives in ports, FYI. > > Also, don't cross post ports issues to current@ > Regards! > -- > Niclas > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" pgpAFw1crTuZU.pgp Description: PGP signature
Re: [PATCH] unbreak imake build when clang set as base compiler
On 2012-09-26 01:13, Eitan Adler wrote: > On 25 September 2012 18:45, Garrett Cooper wrote: >> On Tue, Sep 25, 2012 at 3:37 PM, Oliver Pinter wrote: >>> Hi all! >>> >>> This patch fixed the problem, when buildig imake on a machine where >>> clang is the base the compiler (WITH_CLANG_IS_CC). >> >> (Picking a random message to reply to) Why not create PRs and CC the >> relevant parties? The issue, as Jan pointed out in another thread, is that ucpp isn't compatible with gnu cpp either. It causes other issues, the only difference is that it passes the configure script test. In my opinion, the solution to this problem is to fix the (X11) ports that abuse cpp, and deprecate imake. Also, don't cross post ports issues to current@ Regards! -- Niclas ___ 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: ports/17179: commit references a PR
The following reply was made to PR ports/17179; it has been noted by GNATS.
From: dfil...@freebsd.org (dfilter service)
To: bug-follo...@freebsd.org
Cc:
Subject: Re: ports/17179: commit references a PR
Date: Wed, 26 Sep 2012 08:54:51 + (UTC)
Author: araujo
Date: Wed Sep 26 08:54:40 2012
New Revision: 304887
URL: http://svn.freebsd.org/changeset/ports/304887
Log:
- Update to 2.0.5.
PR: ports/170481 [1], ports/17179 [2]
Submitted by:Geoffroy Desvernay [1],
Sergey Zaykov [2]
Modified:
head/net-mgmt/ocsinventory-agent/Makefile
head/net-mgmt/ocsinventory-agent/distinfo
head/net-mgmt/ocsinventory-ng/Makefile
head/net-mgmt/ocsinventory-ng/distinfo
Modified: head/net-mgmt/ocsinventory-agent/Makefile
==
--- head/net-mgmt/ocsinventory-agent/Makefile Wed Sep 26 08:46:40 2012
(r304886)
+++ head/net-mgmt/ocsinventory-agent/Makefile Wed Sep 26 08:54:40 2012
(r304887)
@@ -1,12 +1,7 @@
-# New ports collection makefile for: ocsinventory-agent
-# Date created: 14 August 2007
-# Whom: Dennis Cabooter
-#
# $FreeBSD$
-#
PORTNAME= Ocsinventory
-PORTVERSION= 2.0.4
+PORTVERSION= 2.0.5
PORTEPOCH=1
CATEGORIES= net-mgmt
MASTER_SITES=
http://launchpad.net/ocsinventory-unix-agent/stable-2.0/${PORTVERSION}/+download/
Modified: head/net-mgmt/ocsinventory-agent/distinfo
==
--- head/net-mgmt/ocsinventory-agent/distinfo Wed Sep 26 08:46:40 2012
(r304886)
+++ head/net-mgmt/ocsinventory-agent/distinfo Wed Sep 26 08:54:40 2012
(r304887)
@@ -1,2 +1,2 @@
-SHA256 (Ocsinventory-Unix-Agent-2.0.4.tar.gz) =
fbfe10915f1de4c48b0da633c89a2c74fd80a77581670871a1eab1bee83ae265
-SIZE (Ocsinventory-Unix-Agent-2.0.4.tar.gz) = 1692852
+SHA256 (Ocsinventory-Unix-Agent-2.0.5.tar.gz) =
7ef1c25dce5f1e0854abc423513c1733219cc73e4c36057dbdad6757e1609a64
+SIZE (Ocsinventory-Unix-Agent-2.0.5.tar.gz) = 1707443
Modified: head/net-mgmt/ocsinventory-ng/Makefile
==
--- head/net-mgmt/ocsinventory-ng/Makefile Wed Sep 26 08:46:40 2012
(r304886)
+++ head/net-mgmt/ocsinventory-ng/Makefile Wed Sep 26 08:54:40 2012
(r304887)
@@ -1,9 +1,9 @@
# $FreeBSD$
PORTNAME= ocsinventory-ng
-PORTVERSION= 2.0.4
+PORTVERSION= 2.0.5
CATEGORIES= net-mgmt
-MASTER_SITES= https://launchpadlibrarian.net/91230684/
+MASTER_SITES= https://launchpadlibrarian.net/99500930/
DISTNAME= OCSNG_UNIX_SERVER-${PORTVERSION}
MAINTAINER= ara...@freebsd.org
Modified: head/net-mgmt/ocsinventory-ng/distinfo
==
--- head/net-mgmt/ocsinventory-ng/distinfo Wed Sep 26 08:46:40 2012
(r304886)
+++ head/net-mgmt/ocsinventory-ng/distinfo Wed Sep 26 08:54:40 2012
(r304887)
@@ -1,2 +1,2 @@
-SHA256 (OCSNG_UNIX_SERVER-2.0.4.tar.gz) =
e140dc9b1ddac45154add360ac2552e643171cb602f93c7c1d629d9c2445f28c
-SIZE (OCSNG_UNIX_SERVER-2.0.4.tar.gz) = 1973117
+SHA256 (OCSNG_UNIX_SERVER-2.0.5.tar.gz) =
3e5c7ce7ee6320d143e0dafa30909070c23313ccd4deaeef3b883a4aa66e9369
+SIZE (OCSNG_UNIX_SERVER-2.0.5.tar.gz) = 1966036
___
svn-ports-...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/svn-ports-all
To unsubscribe, send any mail to "svn-ports-all-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Antwort
Sehr geehrte Damen und Herren, nach unserem Besuch Ihrer Homepage möchten wir Ihnen ein Angebot von Produkten vorstellen, das Ihnen ermöglichen wird, den Verkauf Ihrer Produkte sowie Dienstleistungen deutlich zu erhöhen. Unser Angebot beinhaltet Datenbanken mit den Adressen deutscher Firmen, respektive potentiellen Kunden für Ihr Unternehmen. Die Datenbanken der Firmen sind in für Sie interessante und relevante Zielgruppen untergliedert. Die Firmenangaben beinhalten: Name der Firma, Ansprechpartner, E-mail Adresse, Tel. + Fax-Nr., PLZ, Ort, Straße etc. Die Verwendungsmöglichkeiten der Datenbanken sind praktisch unbegrenzt und Sie können durch Verwendung der von uns entwickelten Programme des personalisierten Versendens von Angeboten u.ä. mittels E-mailing bzw. Fax effektive und sichere Werbekampagnen damit durchführen. Bitte informieren Sie sich über die weiteren Details einmal unverbindlich auf unseren Webseiten: http://www.deucom.net Wir würden uns freuen, wenn unsere Datenbanken sowie Programme Ihren Vorstellungen des innovativen Bewerbens potentieller Neukunden entsprechen und stehen Ihnen gerne jederzeit zur Beantwortung Ihrer Fragen zur Verfügung. Mit freundlichen Grüßen http://www.deucom.net --- Wollen Sie keine Infos mehr über unsere Datenbanken erhalten, klicken Sie bitte den Link an und melden sich ab: http://www.deucom.net/?lang=deu&page=unsubscribe ___ 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: [CORRECTION] Change to the header in ports Makefiles, take two
>> Thomas Abthorpe wrote: > Sometimes, as a result of a repocopy, or changed maintainership, the > Created By and MAINTAINER is no longer in synchronisation. To avoid > confusion, the first line can be removed, optionally leaving us with a one > line header. > > # $FreeBSD$ > > Removing the line of attribution is to be done only at the consent/request > of the original contributor. Why bother? I always thought that this leaving the original maintainer intact is a nice way to say thank you to the person who brought this piece to FreeBSD. //Marcin ___ 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"
