On 9/11/2012 6:32 PM, Olli Hauer wrote:
> On 2012-09-12 00:50, Michael Scheidell wrote:
>> Like with Apache, x 11, or perl?
>> Trying to get something there committed it's like pulling tiger teeth with
>> a pair of pliers. return I agree multiple maintainers is a bad idea.
>> If someone is technica
Two lls.
Direct experience with x 11
But you can see this list for many complaints about trying to get port
committed owned by teams.
Ps I don't troll.
--
Michael Scheidell
Will Hack For Food
___
freebsd-ports@freebsd.org mailing list
http://lists.free
On 2012-09-12 00:50, Michael Scheidell wrote:
> Like with Apache, x 11, or perl?
> Trying to get something there committed it's like pulling tiger teeth with
> a pair of pliers. return I agree multiple maintainers is a bad idea.
> If someone is technical enough to want to maintain that, they can al
On Wed, Sep 12, 2012 at 12:50 AM, Michael Scheidell
wrote:
> Like with Apache, x 11, or perl?
> Trying to get something there committed it's like pulling tiger teeth with a
> pair of pliers. return I agree multiple maintainers is a bad idea.
> If someone is technical enough to want to maintain tha
Like with Apache, x 11, or perl?
Trying to get something there committed it's like pulling tiger teeth with
a pair of pliers. return I agree multiple maintainers is a bad idea.
If someone is technical enough to want to maintain that, they can always
use an alias it goes to a group.
Oh, were talking
On Tue, Sep 11, 2012 at 10:59 PM, Chris Rees wrote:
> As a nice extra, it would also on the surface support multiple
> maintainers and make maintainer would still only return the first
> match.
Multiple maintainers? It's the best way to make no one responsible for
a port: "Should I handle th
I've always relied on local log files, script-generated files, .txt files with
hints on rebuilding, .htm with usage, etc in the ports tree directories
(/usr/ports/devel/subversion/Plist_Manually
/usr/ports/devel/subversion/Time_toCompile
/usr/ports/devel/subversion/svn_ports.msg ) etc etc.
With mo
On 11 September 2012 22:14, Stephen Montgomery-Smith
wrote:
> On 09/11/2012 03:59 PM, Chris Rees wrote:
>>
>> Hi all,
>>
>> Ever since I peeked at OpenBSD's ports [1] to see how they handle
>> headers, I've noticed something else nice that they do.
>>
>> Instead of the plain, boring who-the-hell-i
On 09/11/2012 03:59 PM, Chris Rees wrote:
Hi all,
Ever since I peeked at OpenBSD's ports [1] to see how they handle
headers, I've noticed something else nice that they do.
Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have;
MAINTAINER=cr...@freebsd.org
they have th
On 9/11/2012 3:59 PM, Chris Rees wrote:
> Hi all,
>
> Ever since I peeked at OpenBSD's ports [1] to see how they handle
> headers, I've noticed something else nice that they do.
>
> Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we
> have;
>
> MAINTAINER=cr...@freebsd.or
Hi all,
Ever since I peeked at OpenBSD's ports [1] to see how they handle
headers, I've noticed something else nice that they do.
Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have;
MAINTAINER=cr...@freebsd.org
they have the much more pleasant and personal style;
MA
On Tue, 11 Sep 2012, Chris Rees wrote:
I haven't seen this asked so far so I'll do it. Is there a cookbook
procedure to create a local svn server similar to the one you posted for a
single machine update?
f.e.:
[1] create user, group and directory
[2] cd /
[3] su
[4] svn ...
etc.
I have re
On 9/11/2012 8:06 AM, Frank Seltzer wrote:
> I haven't seen this asked so far so I'll do it. Is there a cookbook
> procedure to create a local svn server similar to the one you posted
> for a single machine update?
>
It takes less time to just follow the instructions footnoted in the
original post
On 11 September 2012 14:06, Frank Seltzer wrote:
>
>
> On Mon, 10 Sep 2012, Kevin Oberman wrote:
>
>> If you want ot update all graphics ports, 'svn up
>> /usr/ports/graphics'. For just updating a single port, 'svn up
>> /usr/ports/graphics/ImageMagick'.
>>
>> But it appears that you chose to not
Synopsis: New port: databases/py-mysql2pgsql [redports]
Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Changed-By: rm
Responsible-Changed-When: Tue Sep 11 18:51:49 UTC 2012
Responsible-Changed-Why:
Should be 'freebsd-ports-bugs', not 'freebsd-ports'.
http://www.freebs
Synopsis: New port: databases/py-mysql2pgsql [redports]
State-Changed-From-To: feedback->open
State-Changed-By: rm
State-Changed-When: Tue Sep 11 18:48:53 UTC 2012
State-Changed-Why:
Should be 'open', not 'feedback'.
http://www.freebsd.org/cgi/query-pr.cgi?pr=169643
_
Synopsis: New port: databases/py-mysql2pgsql [redports]
Responsible-Changed-From-To: rm->freebsd-ports
Responsible-Changed-By: rm
Responsible-Changed-When: Tue Sep 11 18:47:38 UTC 2012
Responsible-Changed-Why:
Submitter's feedback timeout. Return this to the pool. I'd consult
upstream if this ext
2012/9/4 Bryan Drewery :
>> My proposal:
>> - start an exp-run with FORCE_MAKE_JOBS set
>> - mark all new failures with MAKE_JOBS_UNSAFE
>> - flip the default right after the 9.1 release.
+1 too except for devel/libftdi which just failed on me right now, was
ok after setting MAKE_JOBS_UNSAFE.
--
Hello guys;
- Original Message -
...
>
> 2012/9/11 Doug Barton :
>> Now that we have a new version of libxul in the ports tree, any plans of
>> upgrading swt to take advantage of it? I'd love to get the
>> vulnerabilities in the old version off of my daily periodic.
>
> Meanwhile, I
Hello,
The www/libxul was updated to 10.0. It is mentioned
in UPDATING with some instructions for those wanting
to stay with 1.9.2.
I thought I could go with the new version and updated
www/libxul (using portmaster). It went OK.
Now I can't build some other ports, for example
deskutils/chmsee:
--On September 11, 2012 2:44:03 AM -0700 Doug Barton
wrote:
Doug, as you can already use CLANG instead of GCC now, you will be able
to use GCC instead of CLANG after November 4th.
There's lots of things I _can_ do, what we're discussing is what the
defaults should be.
At the moment the port
2012/9/11 Doug Barton :
> Now that we have a new version of libxul in the ports tree, any plans of
> upgrading swt to take advantage of it? I'd love to get the
> vulnerabilities in the old version off of my daily periodic.
Meanwhile, I've had success with x11-toolkits/swt-devel for
mail/davmail an
On Mon, 10 Sep 2012, Kevin Oberman wrote:
If you want ot update all graphics ports, 'svn up
/usr/ports/graphics'. For just updating a single port, 'svn up
/usr/ports/graphics/ImageMagick'.
But it appears that you chose to not follow the instructions. There is
a reason to delete the existing p
On 09/11/2012 02:27 AM, Lars Engels wrote:
> On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote:
>> As of last week, 4,680 ports out of 23,857 failed to build with clang on
>> 9-amd64. That's almost a 20% failure rate. Until we have better support
>> for either building ports with clang, o
On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote:
> As of last week, 4,680 ports out of 23,857 failed to build with clang on
> 9-amd64. That's almost a 20% failure rate. Until we have better support
> for either building ports with clang, or have better support for the
> idea of a "ports
25 matches
Mail list logo
