On 21/07/2010 23:05, Mark Linimon wrote:
> On Wed, Jul 21, 2010 at 10:21:11PM +0200, Kurt Jaeger wrote:
>>> And is this ok to have two ports with the same name.
>>
>> No, it's bad and should be avoided. I'm pretty sure some
>> portupgrade tool will break.
>
> No, they actually handle it ok. It _i
Usually when I find that a port can't fetch the according distfile I
simply google for the distfile with the following search string (e.g.
for rsync):
intitle:"index of" rsync-3.0.7.tar.gz
This approach almost always delivers plenty of results. I then manually
download one of the results
Christopher Key ha scritto:
> At present, the interaction between portconf and port options is
> somewhat confusing.
It's not completely clear to me if you are referring to my portconf
port. If so, the interaction is really simple: portconf is complementary
to port OPTIONS, that is, it's to be us
Joe wrote:
The text as its currently exists is a long way from being clear to a
first timer. And I am talking about the new change that just went in.
"shar `find port_dir` (note the backticks)",
or
"shar $(find port_dir)"
both address the problem nicely.
By all means go and make the correct
On Thu, 22 Jul 2010 08:00:47 -0400
Frank J. Laszlo articulated:
> I'm not trying to attack the OP, but I wanted to voice my objection for
> dumbing down the handbook to the point that a 3 year old could figure it
> out.
OK, so what age should we use for the cutoff limit? By the way, age is
an
On Thu, 22 Jul 2010, Jerry wrote:
Then again, perhaps we should just remove the handbook all together and
let everyone figure it out for themselves. No dumbing down at all
required. We certainly would not want to over do the 'friendly'
concept. I suppose some of use, you obviously, knew it all w
Quoth Janne Snabb on Thursday, 22 July 2010:
> On Thu, 22 Jul 2010, Jerry wrote:
>
> >Then again, perhaps we should just remove the handbook all together and
> >let everyone figure it out for themselves. No dumbing down at all
> >required. We certainly would not want to over do the 'friendly'
> >c
Quoth Emanuel Haupt on Thursday, 22 July 2010:
> Usually when I find that a port can't fetch the according distfile I
> simply google for the distfile with the following search string (e.g.
> for rsync):
>
> intitle:"index of" rsync-3.0.7.tar.gz
>
> This approach almost always delivers plen
On Jul 22, 2010, at 10:32 , Chip Camden wrote:
> Quoth Emanuel Haupt on Thursday, 22 July 2010:
>>
>> http://people.freebsd.org/~ehaupt/distfile-search/distfile-search
>>
>> Adding the following make magic to /etc/make.conf
>>
>> # distfile search
>> .if defined(DISTFILE_SEARCH_BACKUP)
>> pre-
On Thu, 22 Jul 2010 12:17:31 +0200
Emanuel Haupt wrote:
> Usually when I find that a port can't fetch the according distfile I
> simply google for the distfile with the following search string (e.g.
> for rsync):
>
> intitle:"index of" rsync-3.0.7.tar.gz
>
> This approach almost always de
RW wrote:
> On Thu, 22 Jul 2010 12:17:31 +0200
> Emanuel Haupt wrote:
>
> > Usually when I find that a port can't fetch the according distfile I
> > simply google for the distfile with the following search string
> > (e.g. for rsync):
> >
> > intitle:"index of" rsync-3.0.7.tar.gz
> >
> > T
Ade Lovett wrote:
>
> On Jul 22, 2010, at 10:32 , Chip Camden wrote:
>
> > Quoth Emanuel Haupt on Thursday, 22 July 2010:
> >>
> >> http://people.freebsd.org/~ehaupt/distfile-search/distfile-search
> >>
> >> Adding the following make magic to /etc/make.conf
> >>
> >> # distfile search
> >> .i
We don't support flamewars on FreeBSD lists, so I'm going to ask
everyone to simply stop posting on this thread.
The OP had a good point in that the PH text was not as clear as it could
be. I think I've made an improvement to it, and I'm sensitive to the
argument that $() is not portable, so w
Synopsis: [MAINTAINER] security/botan: update to 1.8.9
State-Changed-From-To: feedback->open
State-Changed-By: niels
State-Changed-When: Thu Jul 22 19:28:22 UTC 2010
State-Changed-Why:
Throw back in the pool. Apologies, I don't want to delay this longer (lack of
time)
Responsible-Changed-From
The following reply was made to PR ports/147935; it has been noted by GNATS.
From: Niels Heinen
To: Lapo Luchini
Cc: bug-follo...@freebsd.org
Subject: Re: ports/147935: [MAINTAINER] security/botan: update to 1.8.9
Date: Thu, 22 Jul 2010 21:30:01 +0200
Hi Lapo,
sorry for delaying this one. I l
Synopsis: [MAINTAINER] security/botan: update to 1.8.9
Responsible-Changed-From-To: ports->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu Jul 22 19:58:19 UTC 2010
Responsible-Changed-Why:
Canonicalize assignment.
http://www.freebsd.org/cgi/query-pr.cgi?pr=147935
I'm trying to update a port that I maintain, but the download is failing.
Here's the actual path of the download:
http://nchc.dl.sourceforge.net/projects/afterglow/files/AfterGlow%201.x/1.6/
But the macro has SF/project/, so the download fails. Did Sourceforge just
change their downloads path?
I'm trying to update the devel/byaccj port, which I maintain. The new version
has made some subtle changes in naming, which have thrown me for a loop;
PORTNAME= byaccj
PORTVERSION= 1.15
DISTFILES= byaccj1.15_src.tar.gz
WRKDIR is work/byaccj1.15 when the files are extracted.
If I don't defin
--On Thursday, July 22, 2010 21:27:29 + "B. Estrade"
wrote:
On Thu, Jul 22, 2010 at 04:24:22PM -0500, Paul Schmehl wrote:
I'm trying to update a port that I maintain, but the download is failing.
Here's the actual path of the download:
http://nchc.dl.sourceforge.net/projects/afterglow/fil
On Thu, Jul 22, 2010 at 04:24:22PM -0500, Paul Schmehl wrote:
> I'm trying to update a port that I maintain, but the download is failing.
> Here's the actual path of the download:
> http://nchc.dl.sourceforge.net/projects/afterglow/files/AfterGlow%201.x/1.6/
>
> But the macro has SF/project/, so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Schmehl wrote:
> I'm trying to update the devel/byaccj port, which I maintain. The new
> version has made some subtle changes in naming, which have thrown me for
> a loop;
>
> PORTNAME= byaccj
> PORTVERSION= 1.15
> DISTFILES= byaccj1.15_src.ta
Anonymous wrote:
> >> Am I the only one that thinks it's odd that in 2010 we're still using
> >> executable scripts to distribute text files?
> > How would you do it differently?
> $ diff -upNr /nonexistent mynewport
I quite like this solution. It's a simple command, very similar to
what's used
--On Thursday, July 22, 2010 18:00:32 -0400 Greg Larkin
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Schmehl wrote:
I'm trying to update the devel/byaccj port, which I maintain. The new
version has made some subtle changes in naming, which have thrown me for
a loop;
PORTNAME=
On Thu, 2010-07-22 at 16:24:22 -0500, Paul Schmehl wrote:
> I'm trying to update a port that I maintain, but the download is
> failing. Here's the actual path of the download:
> http://nchc.dl.sourceforge.net/projects/afterglow/files/AfterGlow%201.x/1.6/
That's the wrong path. Try:
-PORTVERSIO
On Thu, 2010-07-22 at 17:44:44 -0500, Paul Schmehl wrote:
[ .. ]
> The Sourceforge situation is a mess, though. I'm going to have to
> wait for that to get fixed in the macros before I can proceed with
> afterglow.
Please provide some evidence about the brokenness of the SF macros.
--
Sahil T
Strange freecolor behavior on fresh 8.0-RELEASE system.
# uname -a
FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21
15:02:08 UTC 2009 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
amd64
# freecolor -V
freecolor version 0.8.8
# freecolor
Bus error
I have rein
2010/7/23 Randy Belk
> Have you updated your ports? This was an issue on the amd64 distribution,
> but it was fixed.
>
> On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote:
>
>> Strange freecolor behavior on fresh 8.0-RELEASE system.
>>
>> # uname -a
>> FreeBSD alternate-1.net 8.0-RELEASE FreeB
2010/7/23 Antonio Kless
>
>
> 2010/7/23 Randy Belk
>
> Have you updated your ports? This was an issue on the amd64 distribution,
>> but it was fixed.
>>
>> On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote:
>>
>>> Strange freecolor behavior on fresh 8.0-RELEASE system.
>>>
>>> # uname -a
>>>
Have you updated your ports? This was an issue on the amd64 distribution,
but it was fixed.
On Fri, Jul 23, 2010 at 1:21 AM, Antonio Kless wrote:
> Strange freecolor behavior on fresh 8.0-RELEASE system.
>
> # uname -a
> FreeBSD alternate-1.net 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21
> 15:
29 matches
Mail list logo
