> > Unless I hear too many cries "don't do that" (with justification), I
> > plan to not create any perl symlinks in /usr/bin in the forthcoming
> > upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
> > will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
> >
I mean them downloading from the psybnc website and installing from
that tarball, I guess an option I can provide is to compile from ports
and make some sort of script to install the binaries to the user's
dir.
Chris
On Sat, 29 Jan 2005 21:10:53 +1300, Jonathan Chen <[EMAIL PROTECTED]> wrote:
>
Changing this so it affects 5-STABLE is suicide it will annoy a lot of
user's and draw people away from FreeBSD to other platforms, I dont
see any benefit from doing this the symlinks have caused me no ill
effect whatsoever
Chris
On Sat, 29 Jan 2005 22:51:37 -0700, Scott Long <[EMAIL PROTECTED]>
Anton Berezin wrote:
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
On Sat, Jan 29, 2005 at 11:51:36PM -0500, Chuck Swiger wrote:
> Andrew McNaughton wrote:
> #!/usr/bin/env PERL5OPT='-w' perl
"#!/usr/bin/perl -w" sounds much easier.
Edwin
--
Edwin Groothuis |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]| Weblog: http:
Andrew McNaughton wrote:
On Sat, 29 Jan 2005, Chuck Swiger wrote:
[ ... ]
Well-behaved 3rd party scripts ought to start Perl via:
#! /usr/bin/env perl
...so long as /usr/local/bin is in the $PATH, they should still work
fine.
I commonly use this approach, but I run into some problems with flags.
P
On Sat, 29 Jan 2005, Anton Berezin wrote:
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
will ONLY be true for FreeBSD 5.X and FreeBSD C
On Sat, 29 Jan 2005, Chuck Swiger wrote:
Oliver Lehmann wrote:
Anton Berezin wrote:
In practical terms this will mean a one-time sweep of your scripts in
order to convert them, in a typical case, from #! /usr/bin/perl to
#! /usr/local/bin/perl.
Wouldn't that break most of the 3rd party scripts out
On Sun, 30 Jan 2005, Matthias Andree wrote:
Oliver Lehmann <[EMAIL PROTECTED]> writes:
Anton Berezin wrote:
In practical terms this will mean a one-time sweep of your scripts in
order to convert them, in a typical case, from #! /usr/bin/perl to
#! /usr/local/bin/perl.
Wouldn't that break most of t
On Sun, Jan 30, 2005 at 03:39:51AM +0100, Matthias Andree wrote:
> Oliver Lehmann <[EMAIL PROTECTED]> writes:
>
> > Anton Berezin wrote:
> >
> >> In practical terms this will mean a one-time sweep of your scripts in
> >> order to convert them, in a typical case, from #! /usr/bin/perl to
> >> #! /u
Oliver Lehmann <[EMAIL PROTECTED]> writes:
> Anton Berezin wrote:
>
>> In practical terms this will mean a one-time sweep of your scripts in
>> order to convert them, in a typical case, from #! /usr/bin/perl to
>> #! /usr/local/bin/perl.
>
> Wouldn't that break most of the 3rd party scripts out in
On Saturday 29 January 2005 21:24, Anton Berezin wrote:
> Unless I hear too many cries "don't do that" (with justification), I
Please, "don't do that"!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-POLA
--
/"\ Best regards, | [EMAIL PROTECTED]
\ /
Anton,
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
pollution of
On Sat, 2005-Jan-29 21:24:25 +0100, Anton Berezin wrote:
>In practical terms this will mean a one-time sweep of your scripts in
>order to convert them, in a typical case, from #! /usr/bin/perl to
>#! /usr/local/bin/perl.
I'd also like to object. The perl documentation has consistently
stated that
On Jan 29, 2005, at 12:58 PM, Kris Kennaway wrote:
On Sat, Jan 29, 2005 at 09:24:25PM +0100, Anton Berezin wrote:
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang
On Sat, Jan 29, 2005 at 10:17:47PM +0100, Anton Berezin wrote:
> On Sat, Jan 29, 2005 at 10:09:05PM +0100, Oliver Lehmann wrote:
> > Anton Berezin wrote:
> >
> > > In practical terms this will mean a one-time sweep of your scripts in
> > > order to convert them, in a typical case, from #! /usr/bin
Anton Berezin wrote:
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
On 2005-01-29 at 21:24:25 Anton Berezin wrote:
> Unless I hear too many cries "don't do that" (with justification), I
> plan to not create any perl symlinks in /usr/bin in the forthcoming
> upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
> will ONLY be true for FreeBSD 5.X
Chuck Swiger wrote:
Well-behaved 3rd party scripts ought to start Perl via:
#! /usr/bin/env perl
...so long as /usr/local/bin is in the $PATH, they should still work fine.
It seems that this usage is not that common. On my 5.3R system the stats
are:
1101 scripts ending in .pl
490 of these have #
On Sat, 29 Jan 2005, Oliver Lehmann wrote:
> Anton Berezin wrote:
>
> > In practical terms this will mean a one-time sweep of your scripts in
> > order to convert them, in a typical case, from #! /usr/bin/perl to
> > #! /usr/local/bin/perl.
>
> Wouldn't that break most of the 3rd party scripts o
On Fri, 28 Jan 2005, Oren Baum wrote:
> Description of Server configuration and problems.
>
> Configuration:
>
> FreeBSD 4.4-RELEASE
> apache+mod_ssl-1.3.22+2.8.5_1
> mysql-server-3.23.42
> Hard Drive (dual ATA disks, no RAID) on a Dell P4 PowerEDGE server
It bears mentioning again ... these rele
On Sat, Jan 29, 2005 at 04:19:21PM -0500, Chuck Swiger wrote:
> Oliver Lehmann wrote:
> >Anton Berezin wrote:
> >>In practical terms this will mean a one-time sweep of your scripts in
> >>order to convert them, in a typical case, from #! /usr/bin/perl to
> >>#! /usr/local/bin/perl.
> >
> >Wouldn't
Oliver Lehmann wrote:
Anton Berezin wrote:
In practical terms this will mean a one-time sweep of your scripts in
order to convert them, in a typical case, from #! /usr/bin/perl to
#! /usr/local/bin/perl.
Wouldn't that break most of the 3rd party scripts out in the world?
Well-behaved 3rd party scri
On Sat, Jan 29, 2005 at 10:09:05PM +0100, Oliver Lehmann wrote:
> Anton Berezin wrote:
>
> > In practical terms this will mean a one-time sweep of your scripts in
> > order to convert them, in a typical case, from #! /usr/bin/perl to
> > #! /usr/local/bin/perl.
>
> Wouldn't that break most of the
This has a huge external impact. Yes they are easily corrected but
unless there is a specific need to remove them my vote would be to
not put people though such a potentially painful change.
Steve
- Original Message -
From: "Anton Berezin" <[EMAIL PROTECTED]>
In practical terms this wi
Anton Berezin wrote:
> In practical terms this will mean a one-time sweep of your scripts in
> order to convert them, in a typical case, from #! /usr/bin/perl to
> #! /usr/local/bin/perl.
Wouldn't that break most of the 3rd party scripts out in the world?
--
Oliver Lehmann
http://www.pofo.de
On Sat, Jan 29, 2005 at 09:24:25PM +0100, Anton Berezin wrote:
> Unless I hear too many cries "don't do that" (with justification), I
> plan to not create any perl symlinks in /usr/bin in the forthcoming
> upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
> will ONLY be true
On Sat, Jan 29, 2005 at 09:24:25PM +0100, Anton Berezin wrote:
> Unless I hear too many cries "don't do that" (with justification), I
> plan to not create any perl symlinks in /usr/bin in the forthcoming
> upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
> will ONLY be true
Unless I hear too many cries "don't do that" (with justification), I
plan to not create any perl symlinks in /usr/bin in the forthcoming
upgrade of both lang/perl5.8 (to 5.8.6) and lang/perl5 (to 5.6.2). This
will ONLY be true for FreeBSD 5.X and FreeBSD CURRENT; the existing
pollution of /usr/bi
* Admin @ InterCorner <[EMAIL PROTECTED]> [20050129 20:09]:
> I have sent this message before (Wed, 19 Jan 2005 04:11:40 +0100), but
> without respons. So I'll try again.
You didn't provide enough info to help with ACPI debugging
http://www.freebsd.org/doc/en_US.ISO8859
Hi there!
I have sent this message before (Wed, 19 Jan 2005 04:11:40 +0100), but without
respons. So I'll try again.
---
I have gladly installed FreeBSD5 on my laptop to be free from M$ !! :D
And soon I will install it on my worksation aswell.
Here is (in my eyes) an unusual boot error.
When I s
On Sat, Jan 29, 2005 at 02:45:27AM +, Chris wrote:
> I am talking about the psybnc source because its for users on the
> server who cannot compile software from ports.
If they can't compile from ports, then they certainly won't be able to
install it; won't that mean that they won't be able to
32 matches
Mail list logo
