Re: Instafix for FreeBSD ports brokenness on 10.0?
On Thu, 29 Sep 2011 16:12:40 -0700
Stanislav Sedov s...@freebsd.org wrote:
So now tell me how
.if ${OSVERION} SOMETHING
do something
.endif
in bsd.port.mk
is more risky then that particular commit which can potentially break
devel/ for all OSVERSIONs.
+1.
I can't understand why I (and other HEAD users) should wait 9.0-RELEASE
or 'patch' bsd.port.mk after every ports tree update ?
Also, not so long time ago was commits with LICENSE= x11, Eitan, have
you tried to compile it BEFORE commit ? Why now I talking about
multiple exp-runs and risk?
--
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: PHP segmentation faults
Moggie ha scritto: Unfortunately, for some time now, PHP scripts have been producing segmentation faults when executed on one of our systems :( Have you enabled LINK_THR option in php port? -- 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: Instafix for FreeBSD ports brokenness on 10.0?
On 30 Sep 2011 00:14, Stanislav Sedov s...@freebsd.org wrote:
On Thu, 29 Sep 2011 17:40:36 -0400
Eitan Adler li...@eitanadler.com mentioned:
The ports tree can be very fickle and touching a large class of ports
requires multiple exp-runs. Attempting these types of changes
just prior to release adds a degree of risk which no one wants to
accept.
Who don't want to accept this?
Who is making this decision for everyone?
Affecting *every single port* is not a negligible risk.
I can easily commit whatever I want to bsd.ruby.mk right now
affecting all the ports (and nobody will say a word), but we can't
do a conditional fix in bsd.port.mk? I'd say the first one poses
much a higher risk (and I never did a single exp-run for that).
Seriously, just look at the commits happening right now. Here's
one example (the most recent commit, not picking up anything):
15:22 CIA-28 [ports] glarkin * devel/Makefile: - Hook py-zope.interface
to the build
So now tell me how
.if ${OSVERION} SOMETHING
do something
.endif
in bsd.port.mk
is more risky then that particular commit which can potentially break
devel/ for all OSVERSIONs.
bsd.ruby.mk is only included for ports that ask for it- hardly the same.
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
Re: Instafix for FreeBSD ports brokenness on 10.0?
Hi, * Stanislav Sedov s...@freebsd.org, 20110929 22:43: I think this is a good idea. I recommend sending this to re@ and/or core@ for consideration. Personally, I'd love to see this committed ASAP, as I'm unable to do any ports work right now. I've poked portmgr@. :-) -- Ed Schouten e...@80386.nl WWW: http://80386.nl/ pgpsgq9JCe9nI.pgp Description: PGP signature
Re: Linuxulator X11 broken?
On 29 September 2011 12:50, Andrew and...@flarn.com wrote:
I'm seeing broken flash plugin, skype and citrix client all reporting
in one way or other that they can't open display. This is all on
8.2-STABLE FreeBSD 8.2-STABLE #8: Thu Sep 29 10:11:04 BST 2011 built
this morning on amd64.
e.g.
(npviewer.bin:2790): Gtk-WARNING **: cannot open display: :0
*** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC
client connection
part of ktrace of skype failing to launch:
64328 skype CALL linux_socketcall(0x1,0xca00)
64328 skype RET linux_socketcall 7
64328 skype CALL linux_socketcall(0x3,0xca00)
64328 skype STRU struct sockaddr { AF_LOCAL, invalid }
64328 skype RET linux_socketcall -1 errno 2 No such file or directory
64328 skype CALL close(0x7)
64328 skype RET close 0
64328 skype CALL linux_socketcall(0x1,0xca00)
64328 skype RET linux_socketcall 7
64328 skype CALL linux_socketcall(0x3,0xca00)
64328 skype STRU struct sockaddr { AF_LOCAL, /tmp/.X11-unix/X0 }
64328 skype RET linux_socketcall -1 errno 22 Invalid argument
64328 skype CALL close(0x7)
64328 skype RET close 0
64328 skype CALL write(0x6,0x9700e01,0x1)
64328 skype GIO fd 6 wrote 1 byte
@
64328 skype RET write 1
64328 skype CALL close(0x6)
64328 skype RET close 0
64328 skype CALL close(0x5)
64328 skype RET close 0
64328 skype CALL linux_rt_sigaction(0x11,0xca28,0xc99c,0x8)
64328 skype RET linux_rt_sigaction 0
64328 skype CALL linux_exit_group(0x1)
I've reinstalled linux-f10* ports to see if anything changed, but to no avail.
Commenting out the sizeof(sockaddr_un) checks and re-compiling my
kernel gets linuxulator things working again.
Looking at the above ktrace shows a struct sockaddr rather than
sockaddr_un? Does this make these checks wrong (at least for
linuxulator)?
Regards,
Andrew
___
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: Instafix for FreeBSD ports brokenness on 10.0?
On 30 Sep 2011 09:41, Ed Schouten e...@80386.nl wrote: Hi, * Stanislav Sedov s...@freebsd.org, 20110929 22:43: I think this is a good idea. I recommend sending this to re@ and/or core@ for consideration. Personally, I'd love to see this committed ASAP, as I'm unable to do any ports work right now. I've poked portmgr@. :-) But portmgr has already replied... 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
Re: Linuxulator X11 broken?
On Sep 30, 2011, at 8:50 AM, Andrew wrote: On 29 September 2011 12:50, Andrew and...@flarn.com wrote: I'm seeing broken flash plugin, skype and citrix client all reporting in one way or other that they can't open display. This is all on 8.2-STABLE FreeBSD 8.2-STABLE #8: Thu Sep 29 10:11:04 BST 2011 built this morning on amd64. e.g. (npviewer.bin:2790): Gtk-WARNING **: cannot open display: :0 *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection part of ktrace of skype failing to launch: .. I've reinstalled linux-f10* ports to see if anything changed, but to no avail. Commenting out the sizeof(sockaddr_un) checks and re-compiling my kernel gets linuxulator things working again. Looking at the above ktrace shows a struct sockaddr rather than sockaddr_un? Does this make these checks wrong (at least for linuxulator)? It will always do that. There's a linuxolator bug in the kernel that the latest SAs unhid. People are working on it but it'll need fixing in all security branches so it's not a 3 minute task unfortunately. /bz -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: Instafix for FreeBSD ports brokenness on 10.0?
On Fri, Sep 30, 2011 at 09:57:14AM +0100, Chris Rees wrote: On 30 Sep 2011 09:41, Ed Schouten e...@80386.nl wrote: Hi, * Stanislav Sedov s...@freebsd.org, 20110929 22:43: I think this is a good idea. I recommend sending this to re@ and/or core@ for consideration. Personally, I'd love to see this committed ASAP, as I'm unable to do any ports work right now. I've poked portmgr@. :-) But portmgr has already replied... Indeed and the answer hasn't changed. Ports on HEAD are only provided best effort, for regression testing etc, and users of HEAD are expected to be techincally savvy enough to work around potential problems themselves. Feel free to apply Ed's patch locally, but it won't make it into CVS. That said, this patch is the wrong place to fix a problem to autotools. It needs to be fixed in autotools, not bsd.port.mk. No matter if it's bsd.ports.mk or autotools, such a fix needs proper testing, for which we do not currently have the resources as we are concentrating on releasing 9.0. I would suggest you do the same and make 9.0 the best release possible during the next few weeks, after that we'll start looking into 10.0. Erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@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: Linuxulator X11 broken?
On 30 September 2011 10:08, Bjoern A. Zeeb b...@zabbadoz.net wrote: On Sep 30, 2011, at 8:50 AM, Andrew wrote: On 29 September 2011 12:50, Andrew and...@flarn.com wrote: I'm seeing broken flash plugin, skype and citrix client all reporting in one way or other that they can't open display. This is all on 8.2-STABLE FreeBSD 8.2-STABLE #8: Thu Sep 29 10:11:04 BST 2011 built this morning on amd64. e.g. (npviewer.bin:2790): Gtk-WARNING **: cannot open display: :0 *** NSPlugin Wrapper *** ERROR: failed to initialize plugin-side RPC client connection part of ktrace of skype failing to launch: .. I've reinstalled linux-f10* ports to see if anything changed, but to no avail. Commenting out the sizeof(sockaddr_un) checks and re-compiling my kernel gets linuxulator things working again. Looking at the above ktrace shows a struct sockaddr rather than sockaddr_un? Does this make these checks wrong (at least for linuxulator)? It will always do that. There's a linuxolator bug in the kernel that the latest SAs unhid. People are working on it but it'll need fixing in all security branches so it's not a 3 minute task unfortunately. Thanks, not in a rush, I understand making sure the fix is correct whilst maintaining the security and applying it to all the branches is more involved. Andrew ___ 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
recent ports removal
Hi, Doug. You just removed www/pyblosxom. But we have a pr, that update it to latest (not-vulnerable) version: http://bugs.freebsd.org/160682. Please revert. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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
undefined reference to ...
Hiya
Im trying to upgrade PackageKit, but im getting ...
CC libpackagekit_glib2_la-pk-media-change-required.lo
CC libpackagekit_glib2_la-pk-message.lo
CC libpackagekit_glib2_la-pk-package.lo
CC libpackagekit_glib2_la-pk-package-id.lo
CC libpackagekit_glib2_la-pk-package-ids.lo
CC libpackagekit_glib2_la-pk-package-sack.lo
CC libpackagekit_glib2_la-pk-package-sack-sync.lo
CC libpackagekit_glib2_la-pk-progress.lo
CC libpackagekit_glib2_la-pk-repo-detail.lo
CC libpackagekit_glib2_la-pk-repo-signature-required.lo
CC libpackagekit_glib2_la-pk-require-restart.lo
CC libpackagekit_glib2_la-pk-results.lo
CC libpackagekit_glib2_la-pk-service-pack.lo
CC libpackagekit_glib2_la-pk-source.lo
CC libpackagekit_glib2_la-pk-task.lo
CC libpackagekit_glib2_la-pk-transaction-past.lo
CC libpackagekit_glib2_la-pk-transaction-list.lo
CC libpackagekit_glib2_la-pk-update-detail.lo
CCLD libpackagekit-glib2.la
CC pk_socket_example-pk-socket-example.o
CCLD pk-socket-example
GISCAN PackageKitGlib-1.0.gir
/usr/include/machine/endian.h:107: syntax error, unexpected '{' in ' return (__extension__ ({
register __uint32_t __X = (_x); __asm (bswap %0 : +r (__X)); __X; }));' at
'{'
/usr/include/machine/endian.h:107: syntax error, unexpected ';' in ' return (__extension__ ({
register __uint32_t __X = (_x); __asm (bswap %0 : +r (__X)); __X; }));' at
';'
/usr/lib/libarchive.so: undefined reference to `lzma_stream_encoder@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_decoder@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_memusage@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_stream_decoder@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_code@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_end@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_lzma_preset@XZ_5.0'
/usr/lib/libarchive.so: undefined reference to `lzma_alone_encoder@XZ_5.0'
linking of temporary binary failed: Command '['/bin/sh', '../../libtool',
'--mode=link', '--tag=CC', '--silent', 'cc', '-o',
'/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11/lib/packagekit-glib2/tmp-introspect40CBf9/PackageKitGlib-1.0',
'-export-dynamic', '-O2', '-pipe', '-fno-strict-aliasing', '-L.',
'libpackagekit-glib2.la', '-pthread', '-L/usr/local/lib', '-lgio-2.0',
'-lgobject-2.0', '-lgmodule-2.0', '-lgthread-2.0', '-lglib-2.0',
'/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11/lib/packagekit-glib2/tmp-introspect40CBf9/PackageKitGlib-1.0.o']'
returned non-zero exit status 1
gmake[4]: *** [PackageKitGlib-1.0.gir] Error 1
gmake[4]: Leaving directory
`/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11/lib/packagekit-glib2'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory
`/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11/lib/packagekit-glib2'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11/lib'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/ports-mgmt/packagekit/work/PackageKit-0.6.11'
gmake: *** [all] Error 2
*** Error code 1
Stop in /usr/ports/ports-mgmt/packagekit.
*** Error code 1
Stop in /usr/ports/ports-mgmt/packagekit.
=== make failed for ports-mgmt/packagekit
=== Aborting update
=== You can restart from the point of failure with this command line:
portmaster flags ports-mgmt/packagekit
I looked at /usr/ports/UPDATING
And I tried
portupgrade -o archivers/xz lzmautils\*
and Im stilling getting this error. Please could someone assist.
Regards
Brent Clark
___
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: PHP segmentation faults
On 30/09/2011 08:10, Alex Dupre wrote: Moggie ha scritto: Unfortunately, for some time now, PHP scripts have been producing segmentation faults when executed on one of our systems :( Have you enabled LINK_THR option in php port? The LINK_THR option was not enabled. I've just enabled it and rebuilt the PHP ports, it seems the segmentation fault error has gone away now, yay! Thank you :) ___ 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: PHP segmentation faults
There is a thread in the archive that discusses this issue. The thread subject is php5-5.3.6_1 with Segmentation fault (amd64) Check item 101 in the following page: http://docs.freebsd.org/mail/archive/2011/freebsd-ports/20110703.freebsd-ports.html Hope this works. Cheers On Fri, Sep 30, 2011 at 8:14 AM, Moggie mog...@elasticmind.net wrote: On 30/09/2011 08:10, Alex Dupre wrote: Moggie ha scritto: Unfortunately, for some time now, PHP scripts have been producing segmentation faults when executed on one of our systems :( Have you enabled LINK_THR option in php port? The LINK_THR option was not enabled. I've just enabled it and rebuilt the PHP ports, it seems the segmentation fault error has gone away now, yay! Thank you :) __**_ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-portshttp://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscribe@**freebsd.orgfreebsd-ports-unsubscr...@freebsd.org -- Attos Janus ___ 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
FYI: BerliOS will be closed on 31.12.2011
From http://www.berlios.de/: [...] Unfortunately, as a research institute Fraunhofer FOKUS has only few opportunities to operate a repository like BerliOS. Such a project will only work with a follow-up financing, or with sponsors or partners taking over the repository. In the field of OSS this is a difficult undertaking. In a recent survey the community indicated some support in funds and manpower which we would like to thank you for. Unfortunately, the result is not enough to put the project on a sustainable financial basis. In addition the search for sponsors or partners was not successful. Open Source is understood by Fraunhofer FOKUS as a paradigm for future-oriented intelligent use of IT. It hurts us all the more that we are forced to discontinue the hosting for BerliOS by 31.12.2011. [...] -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: recent ports removal
On 09/30/2011 02:54, Ruslan Mahmatkhanov wrote: Doug Barton wrote on 30.09.2011 13:50: On 09/30/2011 02:40, Ruslan Mahmatkhanov wrote: Hi, Doug. You just removed www/pyblosxom. But we have a pr, that update it to latest (not-vulnerable) version: http://bugs.freebsd.org/160682. Julien took that PR, when he's ready to do the update he can pull the files out of the Attic. Doug Ok, but as far i recall, there in ports@ was sounded a policy like we do not remove the ports with open pr's on them. I think you misunderstand what remove means in this context. :) Or perhaps you've never worked with a version control system ... It's honestly hard for me to understand why it's hard for people to understand this concept. When Julien is ready to do his work all he has to do is type 'cvs co -D 2011-09-29 ports/www/pyblosxom ports/www/Makefile' and then do his thing. Because a port has been removed today is completely irrelevant to the possibility that it will come back in a non-vulnerable form tomorrow. Meanwhile, at one point in the past I did do a PR check for most if not all of the ports that I removed, and I have committed several updates from maintainers of ports that I had marked FORBIDDEN/DEPRECATED. In this case because Julien took that PR I assume that he has some sort of special knowledge/interest in the port, and is in the best position to deal with it, so I am deferring to his judgement. In the meantime removing it on schedule is the safest course of action. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) 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: recent ports removal
On 09/30/2011 11:05, Ruslan Mahmatkhanov wrote: Doug Barton wrote on 30.09.2011 22:04: On 09/30/2011 02:54, Ruslan Mahmatkhanov wrote: Doug Barton wrote on 30.09.2011 13:50: On 09/30/2011 02:40, Ruslan Mahmatkhanov wrote: Hi, Doug. You just removed www/pyblosxom. But we have a pr, that update it to latest (not-vulnerable) version: http://bugs.freebsd.org/160682. Julien took that PR, when he's ready to do the update he can pull the files out of the Attic. Doug Ok, but as far i recall, there in ports@ was sounded a policy like we do not remove the ports with open pr's on them. I think you misunderstand what remove means in this context. :) Or perhaps you've never worked with a version control system ... It's [just for thrulz] Yes, it's my second day around the computer system. [/just for thrulz] I meant no offense. I don't know you, so I have no idea what your experience is or isn't. :) I understand that it can be restored in one click, but what the point to remove it in first place if it known that someone already working on it and will undelete it in near time? Because if, for whatever reason, Julien decides not to update it then removing it on schedule is the safest course of action. As far i understand it makes commiter's life little a bit harder No, it really, REALLY doesn't. Seriously. and most important - it confuses the users, who actually using this ports. Which is more confusing to users: 1. Port is scheduled for removal, never gets updated, never gets removed. 2. Port that they cannot install anyway disappears for a short time, then reappears in a usable, non-vulnerable state? Also, please keep in mind that nothing depends on the ports that I removed, so at worst we're talking a minor inconvenience for someone who already has the port installed. Ok, actually i'm asking all this questions in first place because your action on pyblosxom did not conform with this sentence by bapt@: How can ports be removed if the solutions for them is in gnats? They won't before deleting ports, we always check gnats, if a PR exists then we leave the ports so that the PR can be committed http://lists.freebsd.org/pipermail/freebsd-ports/2011-September/069998.html So i'm just curious what is the agreed policy about such ports? Please don't get me wrong. Insert the word permanently in front of deleting in that sentence, and I think you'll get the right idea. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) 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: Instafix for FreeBSD ports brokenness on 10.0?
On Fri, Sep 30, 2011 at 5:10 AM, Erwin Lansing er...@freebsd.org wrote: That said, this patch is the wrong place to fix a problem to autotools. It needs to be fixed in autotools, not bsd.port.mk. No matter if it's bsd.ports.mk or autotools, such a fix needs proper testing, for which we do not currently have the resources as we are concentrating on releasing 9.0. I would suggest you do the same and make 9.0 the best release possible during the next few weeks, after that we'll start looking into 10.0. I have to admit that my reaction is not so much Why won't you fix ports for 10.0 as Why was 9.0 dropped out of CURRENT and 10.0 introduced before 9.0 went STABLE? Jim ___ 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: Instafix for FreeBSD ports brokenness on 10.0?
On Friday 30 September 2011 13:10:20 Jim Trigg wrote: On Fri, Sep 30, 2011 at 5:10 AM, Erwin Lansing er...@freebsd.org wrote: That said, this patch is the wrong place to fix a problem to autotools. It needs to be fixed in autotools, not bsd.port.mk. No matter if it's bsd.ports.mk or autotools, such a fix needs proper testing, for which we do not currently have the resources as we are concentrating on releasing 9.0. I would suggest you do the same and make 9.0 the best release possible during the next few weeks, after that we'll start looking into 10.0. I have to admit that my reaction is not so much Why won't you fix ports for 10.0 as Why was 9.0 dropped out of CURRENT and 10.0 introduced before 9.0 went STABLE? Jim At this point 9.0 and 10.0 are virtually identical. I really doubt that there will be much development in -CURRENT till after 9.0 is released anyway. A couple of the temporary fixes worked for me, so I can still update if I need to. All in all this is minor compared to a few years ago when all development was done directly on the head branch. You never knew from day to day and sometimes by the hour if -CURRENT would even build let alone run. This is just a bump in the road by comparison. Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/8.2R/announce.html --- ___ 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
Setting up environment for development/testing
Hi all, Could anyone give me some hints on how to set up an environment to develop and test new ports? I see some people use tinderbox. Are tinderbox's jails the best way to write and test ports? What are the alternatives? Would be enough to have a fresh freebsd installation on a virtual machine or is it better to prepare a chroot? I read the porter's handbook but it didn't seem too clear to this respect. Any other information source that I should refer to? Sorry if these are too many questions... just one more :) could you cc me? I'm not subscribed to the list. Thanks in advance. ___ 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: Replacing procmail with maildrop
On Thu, 29 Sep 2011 05:55:24 +1000 andrew clarke m...@ozzmosis.com wrote: Thanks for that. Looks like I'll be migrating across to maildrop in the next week or so :-) Something you may want to add is that if you use Maildir format and have this in ~/.procmailrc: DEFAULT=$HOME/Maildir/ You need the equivalent for maildrop's ~/.mailfilter: DEFAULT=$HOME/Maildir/ Without this, messages that were not filtered (ie. fell through) will be appended to the mbox file, /var/mail/$USER. On a similar note, if you use MH-style mail folders, something like this: DEFAULT=| rcvstore +inbox (with a properly set PATH, of course) Once I actually set about in earnest today to convert my .procmailrc to .mailfilter format, I was amazed how easy it turned out to be. My one remaining little bug-a-boo is with maildrop's logging; it wants to overwrite the log on each invocation instead of appending. Still no clue how to fix that. But otherwise, the transition was really a breeze, and is working just fine. -- Conrad J. Sabatier conr...@cox.net ___ 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
