Re: Time to mark portupgrade deprecated?

On 07/25/2011 04:20 AM, Eitan Adler wrote: > At this point noone is maintaining portupgrade any more and a large > number of PRs have been filed against it (see > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No > one has stepped up to do the work to fix these bugs so it is tim

Re: Time to mark portupgrade deprecated?

On Mon, 2011-07-25 at 09:33 +0200, Tilman Keskinöz wrote: > I am ok with switching the documentation to portmaster, but i am against > marking it DEPRECATED. I have been using portupdate for 10 years and it > works for all my usecases. > > Switching to portmaster means i have to learn new -option

Re: Time to mark portupgrade deprecated?

Am 25.07.2011 10:50, schrieb Michal Varga: > Sure, by that time I spent on writing this email, I might have been > halfway through portmaster documentation and have my questions answered, > but that's obviously not the point - I just don't need, and don't want > to. You will do once it's the only

Re: Time to mark portupgrade deprecated?

Change is hard. :) I have no objections to someone (or some group) choosing to maintain portupgrade. I've always said that I don't regard portmaster and portupgrade to be in competition. However if no one steps up to maintain it, portupgrade will eventually bitrot and become unusable. So for all

Re: Time to mark portupgrade deprecated?

On Mon, 2011-07-25 at 02:42 -0700, Doug Barton wrote: > Change is hard. :) In fact, that's the whole point of the story, ironically or not. > I have no objections to someone (or some group) choosing to maintain > portupgrade. I've always said that I don't regard portmaster and > portupgrade to b

Re: Time to mark portupgrade deprecated?

On Mon, Jul 25, 2011 at 12:14:19PM +0200 I heard the voice of Michal Varga, and lo! it spake thus: > > I have no objections in [portmaster's] promotion to new users as the > new, one and only "approved" way of managing ports, but this in no > way cuts it for currently deployed portupgrade setups, w

Re: [Announcement] TeX Live 2011: Extended FreeBSD support

On Sat, 23 Jul 2011 21:49:20 +0200, C-S wrote: > First of all, this is great news. > My question is: what is the reason for not creating a port given that > you claim in your README.txt file that these binaries have been built in > jails with minimal dependencies. This means that you have figured o

Re: Time to mark portupgrade deprecated?

On Mon, 25 Jul 2011 12:14:19 +0200 Michal Varga articulated: > On Mon, 2011-07-25 at 02:42 -0700, Doug Barton wrote: > > Change is hard. :) > > In fact, that's the whole point of the story, ironically or not. > > > I have no objections to someone (or some group) choosing to maintain > > portupgr

Current unassigned ports problem reports

(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsol

Re: Kernel Intel GPU driver and ports

on 23/07/2011 16:51 Koop Mast said the following: > svn co http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev svn: The OPTIONS response did not include the requested activity-collection-set; this often means that the URL is not WebDAV-enabled I am not an svn power user - is there anyt

Re: Time to mark portupgrade deprecated?

My two cents after reading this whole thread: like it or not, portupgrade is currently the "official" tool (it's in the Handbook and all other docs). So in my view, this is what needs to be done: a) select a new "official tool" b) create or update said tool so it is working to 95% of all the wishe

Re: Time to mark portupgrade deprecated?

On 25 July 2011 12:27, Torfinn Ingolfsen wrote: > My two cents after reading this whole thread: > > like it or not, portupgrade is currently the "official" tool (it's in > the Handbook and all other docs). > So in my view, this is what needs to be done: > a) select a new "official tool" > b) creat

Re: Time to mark portupgrade deprecated?

On 07/25/2011 04:20 AM, Eitan Adler wrote: > At this point noone is maintaining portupgrade any more and a large > number of PRs have been filed against it (see > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No > one has stepped up to do the work to fix these bugs so it is tim

Re: Sponsoring ports

Hi, Francisco. Francisco Reyes wrote on 25.07.2011 07:52: Is there a list/page somewhere of port commiters willing to do paid work for sponsored ports? Would be great to have a list of such developers at http://wiki.freebsd.org/WantedPorts I am looking for someone to work on porting http://pyp

Re: Sponsoring ports

On 25 Jul 2011 05:16, "Francisco Reyes" wrote: > > Is there a list/page somewhere of port commiters willing to do paid work for sponsored ports? > > Would be great to have a list of such developers at > http://wiki.freebsd.org/WantedPorts > > I am looking for someone to work on porting http://pypy

Re: Time to mark portupgrade deprecated?

On Mon, 25 Jul 2011, Michal Varga wrote: 3. Switching to portmaster means retraining for a different *mission critical* software, that behaves differently, and that I currently have no need for, because the former one works fine. To point out a specific examply that I see frequently in UPDATING:

Re: Time to mark portupgrade deprecated?

On Mon, Jul 25, 2011 at 08:33:24AM -0600, Warren Block wrote: > ... > portmaster ... > But the overall killer feature is active maintenance. Well, that, and the fact that portmaster doesn't depend on bits that it is upgrading. Peace, david (who used to use portupgrade, but switched some time ag

[ANNOUNCE]: clang compiling ports, take 2

Hi! Flz@ just run another exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ Since the last run we've managed to fix the biggest offenders but that uncovered others that need fixing. Th

Re: Sponsoring ports

On 7/25/11 10:30 AM, Chris Rees wrote: > If anyone knows of developer(s) or is such developer please drop me a line with estimate cost. > This is "personal sponsoring" (no company... just me..) so please be gentle on the estimate. :-) Assume we all are, and put an offer on the Wiki page :P

Re: [ANNOUNCE]: clang compiling ports, take 2

On Mon, Jul 25, 2011 at 05:59:20PM +0200, Roman Divacky wrote: > Hi! > > > Flz@ just run another exp-build with CC=clang and CXX=clang++. The results > can be > seen here: > > > http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ > It would be good to also

Re: Sponsoring ports

> Got two replies and working with one of the responders. Cool! Thanks for offering this. > > So, would a good process be to put a note on Wiki and email list or just put > in Wiki and see if someone picks up? No. (a) That would be a polling requirement on the developers and (b) only developers

Re: Sponsoring ports

On 7/25/11 2:04 PM, Eitan Adler wrote: We probably should have a dedicated system for handling these types of requests. As long as the volume stays small sending mail to -ports (like you did) is probably the best way for now Agree. For contract/long term tasks sure.. jobs is the right place, b

Re: Sponsoring ports

> Agree. > For contract/long term tasks sure.. jobs is the right place, but we should > have a place where people can "sponsor" short, specific, features in > FreeBSD. It may be more than just ports, it may also be functionally changes > to the OS. This often results in people offering very low su

Re: Sponsoring ports

On 7/25/11 2:52 PM, Test Rat wrote: Why not contact someone who is already working on it? http://docs.freebsd.org/cgi/mid.cgi?201106082125.56696.naylor.b.david Thanks for the link. I searched for "pypy freebsd" and a few other variations and did not see the link. _

Re: Time to mark portupgrade deprecated?

On Sunday 24 July 2011 18:30:04 Steve Wills wrote: > On 07/24/11 22:20, Eitan Adler wrote: > > At this point noone is maintaining portupgrade any more and a large > > number of PRs have been filed against it (see > > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=portupgrade). No > > one has

Re: Sponsoring ports

Francisco Reyes writes: > Is there a list/page somewhere of port commiters willing to do paid > work for sponsored ports? > > Would be great to have a list of such developers at > http://wiki.freebsd.org/WantedPorts > > I am looking for someone to work on porting http://pypy.org Why not contact

Re: Sponsoring ports

On Mon, Jul 25, 2011 at 1:53 PM, Eitan Adler wrote: > > Agree. > > For contract/long term tasks sure.. jobs is the right place, but we > should > > have a place where people can "sponsor" short, specific, features in > > FreeBSD. It may be more than just ports, it may also be functionally > chang

Re: [ANNOUNCE]: clang compiling ports, take 2

On Mon, Jul 25, 2011 at 6:59 PM, Roman Divacky wrote: > Hi! > > > Flz@ just run another exp-build with CC=clang and CXX=clang++. The results > can be > seen here: > > > http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ > > > Since the last run we've managed to fix the

Re: Sponsoring ports

On 25 Jul 2011 19:05, "Eitan Adler" wrote: > > No. (a) That would be a polling requirement on the developers and (b) > only developers have access to the wiki. > Anyone in ContributorsGroup (basically any verified human) has write access to the Wiki. The only developer perks are the ability to ad

Re: Time to mark portupgrade deprecated?

Hi, On Mon, Jul 25, 2011 at 1:40 PM, Chris Rees wrote: > On 25 July 2011 12:27, Torfinn Ingolfsen wrote: >> My two cents after reading this whole thread: >> >> like it or not, portupgrade is currently the "official" tool (it's in >> the Handbook and all other docs). >> So in my view, this is wha

Re: Sponsoring ports

> Anyone in ContributorsGroup (basically any verified human) has write access > to the Wiki. The only developer perks are the ability to add contributors > and a small select number of pages. Per the wiki Note that as a general rule only FreeBSD developers get access to edit this wiki. This is

Re: find-packages-using-libs: request for feedback

This looks useful - any chance you could make a port out of this? On Tue, Jul 12, 2011 at 6:56 PM, Anton Berezin wrote: > Hi, > > After the recent icu and libgcrypt updates I decided to try and find a > way to avoid rebuilding everything which depends on a particular > port when its shared libra

Re: Time to mark portupgrade deprecated?

> Why pick portupgrade when a lot of people (including myself) use it? There > are > probably 100's of ports more worthy of deprecation. Maybe there should be a > policy to deprecate all unmaintained ports if nobody steps up. You can always > drag it out of the attic if enough people squak and

audio/umurmur needs updating

This port was added but has not been updated. When I created the following PR ( http://www.freebsd.org/cgi/**query-pr.cgi?pr=157100 ) ... this port wasn't in the repository yet. Please commit the newer version of this port found at the link prov

Re: FreeBSD Ports: sylpheed, gnash, seamonkey

Hello, On Wed, Jun 29, 2011 at 10:47 AM, Marco Alberoni wrote: > Hello everybody, I usually use the applications Sylpheed, Gnash and > Seamonkey, and for all of them there the FreeBSD port is not "synchronized" > with the latest available version: are there any problems for their upgrade? Sylphe

Re: FreeBSD Ports: sylpheed, gnash, seamonkey

It's updating to 3.1.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/158798 I guess this will be committed soon. Or you can just patch and try it earlier. On Mon, Jul 25, 2011 at 4:25 PM, Torfinn Ingolfsen wrote: > Hello, > > On Wed, Jun 29, 2011 at 10:47 AM, Marco Alberoni wrote: >> Hello ev

Re: Time to mark portupgrade deprecated?

On 07/25/2011 03:42, Matthew D. Fuller wrote: > On Mon, Jul 25, 2011 at 12:14:19PM +0200 I heard the voice of > Michal Varga, and lo! it spake thus: >> >> I have no objections in [portmaster's] promotion to new users as the >> new, one and only "approved" way of managing ports, but this in no >> wa

Re: [ANNOUNCE]: clang compiling ports, take 2

Roman Divacky writes: > Hi! > > Flz@ just run another exp-build with CC=clang and CXX=clang++. The results > can be > seen here: > > http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ qt4-webkit seems to trigger a clang bug, but the description for clang bug only say

Re: Kernel Intel GPU driver and ports

On Sat, Jul 23, 2011 at 9:45 AM, Andriy Gapon wrote: > on 23/07/2011 16:51 Koop Mast said the following: >> svn co http://trillian.chruetertee.ch/ports/browser/branches/xorg-dev > > svn: The OPTIONS response did not include the requested > activity-collection-set; > this often means that the URL

Re: [ANNOUNCE]: clang compiling ports, take 2

Hi-- On Jul 25, 2011, at 4:31 PM, Raphael Kubo da Costa wrote: >> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/ > > qt4-webkit seems to trigger a clang bug, but the description for clang > bug only says "See (TBA) for further information". Is there anything we > (