Doug Barton wrote:
It might be
simpler just to update to 6.2-RELEASE in the long run.
It's planned, about 3 months from now. Until then... ;-)
--
Jo Rhett
senior geek
Silicon Valley Colocation
___
freebsd-ports@freebsd.org mailing list
http://lists
Jo Rhett schrieb:
Scot Hetzel wrote:
So all of the ports which are being updated to use rcorder are now
breaking on all of the existing 6.0 systems...
It shouldn't break existing systems, as the scripts are still run in
alphabetical order on the 6.0 systems before revision 1.336.2.1 of
/etc/rc
* currently all ports using fortran are unstable. please wait until I announce
about it
current status of migration
wait ... wait for commit approval
source ... f90/f77 sources exist
link ... only exist link against f90/f77 complied libraries
gfortran ... used compiler is gfortran42
f77
Please tell me which port uses Fortran. or link against fortran compiled
programs.
I'll fix them.
-- NAKATA, Maho ([EMAIL PROTECTED])
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send
Hi All,
I'm creating a port for OpenPBX, however it requires a recent SpanDSP,
so I have created spandsp-current to keep inline with development, as
Asterisk for one, relies on the patched version of spandsp that is in
the ports tree.
The port has been tested and checks out fine with portlin
I hope next week. I was on vacation until last week and currently I am very
sick and in bed. :-(
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Koopmann, Jan-Peter wrote:
I hope next week. I was on vacation until last week and currently I am very
sick and in bed. :-(
Doh! Feel better soon :) and thanks for the port...
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/ma
Gabor Kovesdan wrote:
Move the affected scripts to /etc/rc.d.
Ugh. It's non portable and hard to document, compared to "apply this
patch to all 6.0 systems" which I can do via cfengine.
--
Jo Rhett
senior geek
Silicon Valley Colocation
___
freebsd
Quoting Jean-Yves Lefort <[EMAIL PROTECTED]> (Fri, 12 Jan 2007 12:13:06 +0100):
> On Fri, 12 Jan 2007 11:17:26 +0100
> Alexander Leidinger <[EMAIL PROTECTED]> wrote:
>
> > Quoting Jean-Yves Lefort <[EMAIL PROTECTED]> (from Thu, 11 Jan 2007
> > 17:21:36 + (UTC)):
> >
> > > jylefort2007-01-
On Sat, Jan 13, 2007 at 07:40:22PM +0100, Alexander Leidinger wrote:
> Quoting Jean-Yves Lefort <[EMAIL PROTECTED]> (Fri, 12 Jan 2007 12:13:06
> +0100):
>
> > On Fri, 12 Jan 2007 11:17:26 +0100
> > Alexander Leidinger <[EMAIL PROTECTED]> wrote:
> >
> > > Quoting Jean-Yves Lefort <[EMAIL PROTECTE
I'm not sure if there's a policy already, but it seems
we have discussed this before.
Can we limit /usr/ports (the whole ports collection) to
English language and ASCII characters? This restriction
should probably apply to all text data (with possible
exception for patches).
I know many of us wo
On 6/14/06, Simon L. Nielsen <[EMAIL PROTECTED]> wrote:
On 2006.06.13 18:51:48 +0400, Andrew Pantyukhin wrote:
> On 6/13/06, Anish Mistry <[EMAIL PROTECTED]> wrote:
> >On Tuesday 13 June 2006 07:54, Andrew Pantyukhin wrote:
> >> On 6/13/06, Anton Berezin <[EMAIL PROTECTED]> wrote:
> >> > On Tue,
Quoting Kris Kennaway <[EMAIL PROTECTED]> (Sat, 13 Jan 2007 13:42:40 -0500):
> This is likely to break large numbers of ports, so we can only proceed
> if you're willing to deal with that.
I expected that... maybe other people are willing to help too. It's one
of the reasons why I present this pa
Andrew Pantyukhin writes:
> I'm not sure if there's a policy already, but it seems
> we have discussed this before.
>
> Can we limit /usr/ports (the whole ports collection) to
> English language and ASCII characters? This restriction
> should probably apply to all text data (with possible
I have two systems and both want to install math/atlas when I try to update
octave. I have atlas-3.6.0_2,1 installed on both systems.
===> octave-2.1.73_2 depends on executable in : gnuplot - found
===> octave-2.1.73_2 depends on executable in : gfortran42 - found
===> octave-2.1.73_2 depen
Boris Samorodov wrote:
> On Sat, 13 Jan 2007 21:27:49 +0100 [LoN]Kamikaze wrote:
>
>> I have two systems and both want to install math/atlas when I try to update
>> octave. I have atlas-3.6.0_2,1 installed on both systems.
>> ...
>
>> I don't know what might be the cause. What kind of informati
On 1/13/07, Robert Huff <[EMAIL PROTECTED]> wrote:
Andrew Pantyukhin writes:
> I'm not sure if there's a policy already, but it seems
> we have discussed this before.
>
> Can we limit /usr/ports (the whole ports collection) to
> English language and ASCII characters? This restriction
> sho
On Sat, Jan 13, 2007 at 09:27:49PM +0100, [LoN]Kamikaze wrote:
> I have two systems and both want to install math/atlas when I try to update
> octave. I have atlas-3.6.0_2,1 installed on both systems.
>
> ===> octave-2.1.73_2 depends on executable in : gnuplot - found
> ===> octave-2.1.73_2 d
On Sat, 13 Jan 2007 21:27:49 +0100 [LoN]Kamikaze wrote:
> I have two systems and both want to install math/atlas when I try to update
> octave. I have atlas-3.6.0_2,1 installed on both systems.
> ===> octave-2.1.73_2 depends on executable in : gnuplot - found
> ===> octave-2.1.73_2 depends o
On Saturday 13 January 2007 14:19, Andrew Pantyukhin wrote:
> On 6/14/06, Simon L. Nielsen <[EMAIL PROTECTED]> wrote:
> > On 2006.06.13 18:51:48 +0400, Andrew Pantyukhin wrote:
> > > On 6/13/06, Anish Mistry <[EMAIL PROTECTED]> wrote:
> > > >On Tuesday 13 June 2006 07:54, Andrew Pantyukhin wrote:
>
I just discovered a problem with two ports that I maintain, and I need
help figuring out how to fix it. The ports in question are
security/sguil-sensor and security/sguil-server. The problem, which I
just discovered today, is that, if both ports are installed on the same
machine (not the norm
--On January 13, 2007 4:50:04 PM -0600 Paul Schmehl <[EMAIL PROTECTED]>
wrote:
I just discovered a problem with two ports that I maintain, and I need
help figuring out how to fix it. The ports in question are
security/sguil-sensor and security/sguil-server. The problem, which I
just discovere
Andrew Pantyukhin wrote:
> On 1/13/07, Robert Huff <[EMAIL PROTECTED]> wrote:
>>
>> Andrew Pantyukhin writes:
>>
>> > I'm not sure if there's a policy already, but it seems
>> > we have discussed this before.
>> >
>> > Can we limit /usr/ports (the whole ports collection) to
>> > English languag
On 1/14/07, Doug Barton <[EMAIL PROTECTED]> wrote:
Andrew Pantyukhin wrote:
> On 1/13/07, Robert Huff <[EMAIL PROTECTED]> wrote:
>>
>> Andrew Pantyukhin writes:
>>
>> > I'm not sure if there's a policy already, but it seems
>> > we have discussed this before.
>> >
>> > Can we limit /usr/ports
I have completed ports of the sipX 3.6.0 components to FreeBSD.
http://sipx-wiki.calivia.com/index.php/Main_Page
There's quite a bit of code here and I'm interested in having
someone(s) look over the ports (12) I've put together before I
submit them. Please contact me and I'll send you wh
On Sat, 2007-01-13 at 12:21 +, Joe Holden wrote:
> Hi All,
>
> I'm creating a port for OpenPBX, however it requires a recent SpanDSP,
> so I have created spandsp-current to keep inline with development, as
> Asterisk for one, relies on the patched version of spandsp that is in
> the ports t
Andrew Pantyukhin wrote:
> On 1/14/07, Doug Barton <[EMAIL PROTECTED]> wrote:
>> Andrew Pantyukhin wrote:
>> > It depends on what you mean by /status quo/, but in
>> > short, when I look at COMMENT, pkg-descr, pkg-message,
>> > comments in Makefile and other such text data, I
>> > expect to see Eng
Jo Rhett wrote:
> Gabor Kovesdan wrote:
>> Move the affected scripts to /etc/rc.d.
>
> Ugh. It's non portable and hard to document, compared to "apply this
> patch to all 6.0 systems" which I can do via cfengine.
Yeah, I wouldn't go that route either. You should be able to generate
the right pat
28 matches
Mail list logo
