Re: LPPL10 license consequences intended? (arabic/arabtex)
On Sat, Mar 22, 2014 at 12:27:07PM -0700, Kevin Oberman wrote: > On Sat, Mar 22, 2014 at 10:29 AM, John Marino > wrote: > > > In December, Nicola set the license for Arabtex to LPPL10. > > The result is that the port is no longer packagable: > > > > > >> Ignoring arabic/arabtex: License LPPL10 needs confirmation, but > > BATCH is defined > > > build of /usr/ports/arabic/arabtex ended at Mon Mar 17 16:12:44 PDT 2014 > > > > From a quick conversation on IRC, I got the idea that the license was > > correct and many more Tex packages should also have this license. > > If/when that happens, does that mean Tex packages are only to be built > > from source? > > > > Is it correct that LPPL10 can't be built in a batch? > > The impact for DPorts is pretty high because a requirement for a dport > > is that it can produce a binary package so right now it looks like I > > have to prune arabtex. > > > > John > > > > Aside from any possible impact of the license, the Makefile contains: > NO_BUILD= yes > so it ill never be packaged and redistributed. This is not an artifact of > the license and I don't know of the license would also block packaging. > > > I just read over LPPL and it i pretty clear that "Compiled Work" (i.e. the > binary code) may be redistributed: > > 3. You may distribute a Compiled Work that has been generated from a > complete, unmodified copy of the Work as distributed under Clause 2 > above, as long as that Compiled Work is distributed in such a way that > the recipients may install the Compiled Work on their system exactly > as it would have been installed if they generated a Compiled Work > directly from the Work. > > Looking at the port, I see exactly NO modifications to the "Work". This > assumes that arabtex is, itself, part of the official "Distribution" of the > "Current Maintainers". It may be that it is, in fact, a "Derived Work", not > officially blessed by the "Current Maintainers". In that case it could not > be packaged under the terms of clause 3 (quoted above), but other LPPL > ports that are part of the official "Work" could be. > > "Derived Work" may be redistributed as "Compiled Work" if certain > conditions are met. See clause 6 which is quite long and I am not confident > that I understand. (In fact, I'm quite confident that I don't fully > understand it.) > > IANAL, but the text is pretty clear. I just have not spent the time to > confirm whether arabtex is "Work" of the project or "Derived Work" of the > official "Distribution". (Note that quoted terms are legally defined terms > in the license.) > -- > R. Kevin Oberman, Network Engineer, Retired > E-mail: rkober...@gmail.com The usual conditions that to build silently _LICENSE_PERMS_DEFAULT= dist-mirror dist-sell pkg-mirror pkg-sell auto-accept The LPPL* stuff has the provisio _LICENSE_PERMS_LPPL10= dist-mirror dist-sell Likewise, IANAL, but having read through the license multiple times over now, it propose that we probably could drop the specific perms in favour of the default perms. Anybody who IAL care to comment ;) Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpOIwDUIUhlI.pgp Description: PGP signature
Re: LPPL10 license consequences intended? (arabic/arabtex)
On Fri, Mar 28, 2014 at 10:33:25AM +0100, John Marino wrote: > It's been a few days and there's been no response to this. > Should I assume that tabthorpe@ read this but is not prepared to review > his work? There is an old adage about assumptions, I am sure you know what it is. Maybe I am just ignoring you. Maybe, just maybe, my mail system has been sideways for a week, and this is the first time I have been able to sit down and properly catch up on emails. You decide what answer suits you best. > > if that is the case, what is the step forward here? All this license > stuff is a black box to me and I'd really like to see someone designated > as the license "guru" (and similarly a legal guru) to give definite > answers to questions like these. I think that nobody is fully > comfortable with this and everyone expects somebody else to take action. > > I would like a ruling on LPPL10 very soon as it potentially affects many > important tex ports. Who is in a position to make the call? I hesitate > to mail to portmgr@ because my last 3-4 topics have never been resolved > and mostly ignored by them as a group, so saying "send a message to > portmgr@" is equivalent to telling me to send it to a black hole. > (Hopefully with the turnover it's less like this in the future but so > far it seems the same as always) > > I'm not really trying to be provocative but there are a number of > "somebody really should fix that" issues going around but the fixes > aren't getting organized so in the end nothing happens (again, I think > this is do to everyone expecting somebody to organize/lead the effort > before they jump in) > > Regards, > John > Long story short, I have been extremely distracted by life outside of FreeBSD, as a result I will be stepping down from my responsibilities later this spring, as I have not been able to deal with everything on my plate. If you would like to take over the licensing stuff, I will be happy to assign your name to it. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgplug_iK17FY.pgp Description: PGP signature
Re: Maintainer reset of textproc/kdiff3
On Thu, Jan 09, 2014 at 09:44:20PM -0700, Bruce Cran wrote: > I no longer have time to work on FreeBSD: could someone reset the > maintainer of textproc/kdiff3 please? > > -- > Bruce Cran > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Done, thanks for your past maintainership. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgprDdx1F2LcF.pgp Description: PGP signature
Calling all ruby enthusiasts
I have been working toward getting lang/ruby18 removed from the ports tree, it is vulnerable, and no longer supported upstream. If you have been watching the commit logs, you will see the work I have already put into it's removal. My personal thanks to Steve Wills (swills@) for helping me through much of the process. I have made some contact with some of you already about updating some ports, but more work has to be done to get ruby18 removed. You are being contacted because you are a maintainer of one of the ports listed below. The first column is a port that has a DEPRECATED dependency, the second column is the port targeted for removal. Mk/bsd.lua.mk lang/ruby-lua4 devel/rubygem-rascutwww/rubygem-mongerl devel/rubygem-rascutwww/rubygem-mongrel devel/rubygem-ruby-debug-base devel/rubygem-linecache dns/dnsdoctor lang/ruby18 games/magicmaze devel/ruby-sdl japanese/gorua x11-toolkits/ruby-gtk security/flowtagx11-toolkits/ruby-tk sysutils/puppet www/rubygem-mongerl sysutils/puppet27 www/rubygem-mongerl www/aswiki textproc/ruby-amrita www/rubygem-rails www/rubygem-mongerl www/rubygem-staticmatic www/rubygem-mongerl www/tdiary www/ruby-nora www/typowww/rubygem-mongrel_cluster www/typowww/rubygem-rails-app-installer It would appear that making www/rubygem-mongerl* work with ruby19 would be the biggest first step toward the final cleanup. If you have some time, and want to help out, please find a port listed above, fix it for ruby19, and file a PR to get it committed. It is that easy :) Thanks for all your help in advance. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp6GrAhh3_75.pgp Description: PGP signature
Re: Ruby Port error
On Fri, Sep 27, 2013 at 02:16:16PM +0200, Jos Chrispijn wrote: >Justs tried to upgrade ruby but something goes wrong here: >> portupgrade -a >** Port marked as IGNORE: lang/ruby18: >is forbidden: Vulernerable, >[1]http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html >** Listing the failed packages (-:ignored / *:skipped / !:failed) >- lang/ruby18 (marked as IGNORE) >Can you pls provide a fix or should I wait for next upgrade? >Thanks, >Jos Chrispijn > > References > >1. http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html lang/ruby18 is destined for removal on October 10. I would suggest upgrading to lang/ruby19 per the instructions in /usr/port/UPDATING dated 20130527. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpuM_mDUZLA6.pgp Description: PGP signature
[HEADS UP] Ports Slush is now in effect
Just to make it official, the ports hard freeze has been lifted. Ports committers are now able to perform regular updates, just no sweeping commits without prior approval from portmgr. This period of slush will continue until 8.4 is out the door. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. And just remember, PLEASE TRY TO NOT BREAK THE INDEX! Thomas on behalf of portmgr@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Ports Freeze for upcoming 8.4 Release
The FreeBSD Ports Management team as decided to do a hard freeze to co-incide with the release of 8.4-FreeBSD RC1, tentatively scheduled for March 30. During this hard freeze, only security updates, critical fixes, and related fixes related to the clean-up of the tree will be allowed. This is a change from our recent Feature Safe policy. If you want/need something to get into the tree after the freeze, email a patch to portmgr@, and await approval. Once we feel the tree is in good shape for shipping, we will open up for a slush. More details on that once we get closer to release time. Thomas on behalf of portmgr@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Bryan Drewery joins portmgr@
I am pleased to announce that Bryan Drewery, aka bdrewery@, has accepted the gauntlet to work on the FreeBSD Ports Management Team. Bryan first stepped into fray when he first took over portupgrade, then added portmaster to his portfolio, and then joined in with the pkgng devs. He has also been instrutmental in working on poudiere development, an alternative build environment to tinderbox. Please join me in welcoming Bryan to the team. Thomas on behalf of portmgr@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Beat Gaetzi steps down from portmgr@
Beat Gaetzi, aka beat@, recently stepped down from his duties on the FreeBSD Ports Management Team. Beat joined the team in 2011, being instrutmental in migrating the ports tree from CVS to Subversion. Beat also took over the duty of sending pavmails, affectionately renamed beatmails. On behalf of the Ports Management team, we would like to thank Beat for his contribution to the team. Thomas on behalf of portmgr@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] FreeBSD Ports tree has been tagged with RELEASE_7_EOL
The FreeBSD Ports Management Team wishes to remind users that February 28 was the end of support for the Ports Collection for both FreeBSD 7.4 RELEASE and the FreeBSD 7.x STABLE branch. Neither the infrastructure nor individual ports are guaranteed to work on these FreeBSD versions after that date. A tag has be created for users who cannot upgrade for some reason, at which time these users are advised to stop tracking the latest ports repository and use the RELEASE_7_EOL tag instead. While many people still use RELENG_7, it is at the end of its development cycle. The Ports Management team has set the following policies with regard to EOL/EOS of this branch and would like to let developers know that: - We do not require committers/maintainers to support 7.x, although ports will need to be marked as BROKEN/IGNORE if they do not build/run. - Port maintainers are encouraged to accept patches from the community that allow their ports to build and run on 7.x. However, since running on 7.x is no longer a requirement, maintainers may use their discretion in cases where a proposed patch would be disruptive to other supported FreeBSD branches, or would unreasonably impede ongoing maintenance of the port. - We strongly encourage all users and developers to migrate to the FreeBSD 8.x or 9.x branch, both of which is a stable and mature platform, and are now the reference branches for the ports collection. Pleae refer to the FreeBSD Security Officer list of unsupported branches http://www.freebsd.org/security/#unsup ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Mark Linimon steps down from portmgr@
Mark Linimon, aka linimon@, recently stepped down from his duties on the FreeBSD Ports Management Team. Mark joined the team back in 2004, providing nine years of continuity to the Ports Infrastructure. Among the many things Mark did, was maintaining and documenting the current portbuild system that the team uses for -exp runs and package building. With his other bugbuster@ hat on, he played middle man contacting maintainers of BROKEN and DEPRECATED ports. On behalf of the Ports Management team, we would like to thank Mark for his many years of service and dedication, his contributions will be greatly missed. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2013/02/21/linimon-steps-down-from-portmgr/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] FreeBSD 9.1 ports freeze is officially over
Just to make it officially official, the ports feature freeze has been lifted. Ports committers are now entitled to perform sweeping commits. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. And just remember, PLEASE TRY TO NOT BREAK THE INDEX! Thomas on behalf of portmgr@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] decke@ joins portmgr@
The FreeBSD Ports Management team is pleased to welcome Bernhard Froelich, aka decke@, to it's ranks. Bernhard was a long time ports contributor, and received his ports commit bit back in March 2010. More recently, Bernhard was the one responsible for bringing us Redports.org shared tinderbox. Please join me in welcoming decke@ to the team. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/10/19/decke-joins-portmgr/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] pav@ steps down from portmgr@
Pav Lucistnik, aka pav@, recently stepped down from his roll on the FreeBSD Ports Management team. Pav started on portmgr back in November 2006, he was the one responsible for many of the -exp runs over the years. His most dubious claim to fame was talking over the responsibility of krismails. We all looked forwward to our pavmails, right? On behalf of the Ports Management team, we want to thank Pav for his years of service, he will be missed. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/10/19/pav-steps-down-from-portmgr/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Ports Feature Freeze for 9.1
FreeBSD 9.1 RC2 has been pulicly announced, it is now time for the the Ports Feature Freeze. Normal upgrade, new ports, and changes that do not affect other ports will be allowed without prior approval, but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, that is, touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@. Check out http://www.freebsd.org/portmgr/implementation.html#sweeping_changes for what constiutes a sweeping change. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/10/10/ports-feature-freeze-for-9-1/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Change to the header in ports Makefiles, take two
On Mon, Sep 17, 2012 at 04:22:45PM +, Thomas Abthorpe wrote: [...] > > Sometimes, as a result of a repocopy, or changed maintainership, the > Created By and MAINTAINER is no longer in synchronisation. To avoid > confusion, the first line can be removed, to ensure only the MAINTAINER > is contacted. This gives us the following two line header. > > # > # $FreeBSD$ > My apologies, this portion of the text was incorrectly published, a correction has been issued at http://lists.freebsd.org/pipermail/freebsd-ports/2012-September/078319.html Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpMXG6C8pdqY.pgp Description: PGP signature
[CORRECTION] Change to the header in ports Makefiles, take two
It was recently posted on, http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ that we would adopt a new header for the ports Makefiles. The initial discussion seemed to show enough support for the idea of completely stripping the header, leaving only the $FreeBSD$ tag. After the announcement was made, more people stated strong feelings that when and where possible attribution be maintained in the header. A private discussion was held among ports committers, and while opinions were as varied as the individuals who shared them, it was decided to unify on a two line header. # Created by: J.Q. Public # $FreeBSD$ The Whom line from the classic six line header becomes Created By. Sometimes, as a result of a repocopy, or changed maintainership, the Created By and MAINTAINER is no longer in synchronisation. To avoid confusion, the first line can be removed, optionally leaving us with a one line header. # $FreeBSD$ Removing the line of attribution is to be done only at the consent/request of the original contributor. As before, we ask this header only be updated in conjunction with a regular update, as we do not want any unnecessary churn to the repo prior to the pending Ports Feature Freeze. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/09/17/change-to-the-header-in-ports-makefiles-take-two/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Change to the header in ports Makefiles, take two
It was recently posted on, http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ that we would adopt a new header for the ports Makefiles. The initial discussion seemed to show enough support for the idea of completely stripping the header, leaving only the $FreeBSD$ tag. After the announcement was made, more people stated strong feelings that when and where possible attribution be maintained in the header. A private discussion was held among ports committers, and while opinions were as varied as the individuals who shared them, it was decided to unify on a two line header. # Created by: J.Q. Public # $FreeBSD$ The Whom line from the classic six line header becomes Created By. Sometimes, as a result of a repocopy, or changed maintainership, the Created By and MAINTAINER is no longer in synchronisation. To avoid confusion, the first line can be removed, to ensure only the MAINTAINER is contacted. This gives us the following two line header. # # $FreeBSD$ As before, we ask this header only be updated in conjunction with a regular update, as we do not want any unnecessary churn to the repo prior to the pending Ports Feature Freeze. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/09/17/change-to-the-header-in-ports-makefiles-take-two/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Change to the header in ports Makefiles
On Sat, Sep 01, 2012 at 06:42:57AM +, Thomas Abthorpe wrote: > An idea has been floating around for some time, and it was brought up again > on the ports@ mailing list recently, please remove the extraneous header > information from the Makefile, leaving only the $FreeBSD$ id on the first > line. > > It is an idea that is long overdue, so from now on, the other fives lines > shall be removed. > > We do request that this be done sparingly in the short term, as we do not > want to cause any additional churn on the repo as we approach our upcoming > Ports Feature Freeze, still tentatively scheduled for September 7. > > So please proceed only on existing updates. Please do not do any sweeping > commits until we have the ports tree stablised post 9.1 tagging. Also bear > in mind that Redports/QAT queues a job for every change done to a Makefile, > we do not want to overburden the QAT at this time. It is important to allow > this service to run at peek efficiency at this time to ensure it's full > potential as we approach the upcoming Feature Freeze. > > The new look of the Makefile has been document in the Porter's Handbook, > http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html#PORTING-MAKEFILE. > > The next item on the todo list is to update devel/newfile for those that do > a port create. > > > Thomas > on behalf of portmgr@ > > > http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ Cease fire on stripping header information. Seems there is more to the issue that we will need to resolved before we proceed, so please update ports normally, please leave the header intact. If you have already stripped some headers, leave it alone for now. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp1hXTJAt55k.pgp Description: PGP signature
Re: [HEADS UP] Change to the header in ports Makefiles
On Sat, Sep 01, 2012 at 07:27:40AM -0400, Jason E. Hale wrote: > On Saturday, September 01, 2012 06:42:57 Thomas Abthorpe wrote: > > Also bear in mind that Redports/QAT queues a job for every change done to a > > Makefile, we do not want to overburden the QAT at this time. It is important > > to allow this service to run at peek efficiency at this time to ensure it's > > full potential as we approach the upcoming Feature Freeze. > > I think it would be good to note that Redports can be made to ignore a commit > and not queue an unnecessary job by adding: > > Redports: ignore > > to the commit message. > > - Jason Cool thanks, I am still learning the finer points of Redports. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpUsjvnYjggS.pgp Description: PGP signature
[HEADS UP] Change to the header in ports Makefiles
An idea has been floating around for some time, and it was brought up again on the ports@ mailing list recently, please remove the extraneous header information from the Makefile, leaving only the $FreeBSD$ id on the first line. It is an idea that is long overdue, so from now on, the other fives lines shall be removed. We do request that this be done sparingly in the short term, as we do not want to cause any additional churn on the repo as we approach our upcoming Ports Feature Freeze, still tentatively scheduled for September 7. So please proceed only on existing updates. Please do not do any sweeping commits until we have the ports tree stablised post 9.1 tagging. Also bear in mind that Redports/QAT queues a job for every change done to a Makefile, we do not want to overburden the QAT at this time. It is important to allow this service to run at peek efficiency at this time to ensure it's full potential as we approach the upcoming Feature Freeze. The new look of the Makefile has been document in the Porter's Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html#PORTING-MAKEFILE. The next item on the todo list is to update devel/newfile for those that do a port create. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/09/01/change-to-the-header-in-ports-makefiles/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Can we please just remove the old Makefile headers?
On Thu, Aug 30, 2012 at 04:09:00PM -0400, Steven Kreuzer wrote: > > > > So without further ado, this is what we would like to see at the top of > > the makefile > > > > # > > # $FreeBSD$ > > # > > > > PORTNAME= > > > > It is as easy as that :) > > This would make me happy. Another option I would like to throw out there is > to just stick the # $FreeBSD$ at the end of the file so the first line > is PORTNAME= I would much rather see it at the top, retaining the notion of header info at the top of the file. We are officially going from six lines down to one, that is buying us (if you still use an 80x24 window like me) an additional 20% of real estate at the top of the editor. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpSBVqsHks1G.pgp Description: PGP signature
Re: Can we please just remove the old Makefile headers?
On Thu, Aug 30, 2012 at 12:54:17PM -1000, Doug Barton wrote: > On 08/30/2012 09:56 AM, Thomas Abthorpe wrote: > > So without further ado, this is what we would like to see at the top of > > the makefile > > > > # > > # $FreeBSD$ > > # > > > > PORTNAME= > > > > It is as easy as that :) > > I was sort of afraid that would be the answer ... while I realize we > have massive historical precedents for the additional #s above and below > the content, what I was hoping for was that we would make the big break > with hysterical raisins and just make the # $FreeBSD$ the first line of > the file. > > It's a minor issue (and yes, this is a legitimate bikeshed) but to my > way of thinking the extra #s are just wasted space that reduce the > amount of useful data that is presented when you open the file in an > editor. > > I won't lose sleep if we go with the extra #s, but I wanted to at least > raise the issue in case there was still a chance to keep it simple. :) > > Doug Well, since we are going with something new, let us just do it, one line # $FreeBSD$ at the very top. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgprfwLM7abWK.pgp Description: PGP signature
Re: Can we please just remove the old Makefile headers?
On Sun, Aug 26, 2012 at 02:02:47PM -0700, Doug Barton wrote: > The old Makefile headers, ala: > > # New ports collection makefile for:BIND 9.9.x > # Date created: 27 January 2012 > # Whom: dougb > # > # $FreeBSD: head/dns/bind99/Makefile 301487 2012-07-24 19:23:23Z dougb $ > > have not served a purpose for longer than almost anyone who has a ports > commit bit has been around. My proposal is simple, let's remove > everything before the # $FreeBSD$. Traditions are great, particularly when they have meaning. When they just become "Doing it that way because we always done it" is no substitute for maintaining a tradition for a meaningful purpose. > > In the past when this has been proposed the objection was that it would > cause too much churn. If we had done this back when we had 5,000 ports > then we would have solved the problem with less churn, and no drama for > the 15,000 ports that followed. Every day we don't do this we make the > "churn" problem worse, and deepen the roots of something that has no > relevance. > > Can we please just deal with this now and be done with it? ... and yes, > I am volunteering to help with and/or do the work myself. We discussed this on portmgr@, and we have agreed it is time to make the change. We do request that this be done sparingly in the short term, as we do not want to cause any additional churn on the repo as we approach our upcoming Ports Feature Freeze, still tentatively scheduled for September 7. So please proceed only on existing updates. Please do not do any sweeping commits until we have the ports tree stablised post 9.1 tagging. Also bear in mind that Redports/QAT queues a job for every change done to a Makefile, we do not want to overburden the QAT at this time. It is important to allow this service to run at peek efficiency at this time to ensure it's full potential as we approach the upcoming Feature Freeze. So without further ado, this is what we would like to see at the top of the makefile # # $FreeBSD$ # PORTNAME= It is as easy as that :) Thomas on behalf of portmgr@ > > Doug > > -- > > I am only one, but I am one. I cannot do everything, but I can do > something. And I will not let what I cannot do interfere with what > I can do. > -- Edward Everett Hale, (1822 - 1909) > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp2TUUaac02a.pgp Description: PGP signature
[HEADS UP] Change in the FreeBSD Ports Management Team
Florent Thoumie, aka flz@, recently stepped down from his roll on the FreeBSD Ports Management team. Florent started on portmgr back in August 2008, being instrumental in maintaining the legacy pkg_* code plus other aspects of the ports infrastructure, including but not limited to the unifying of the code base for the ports build system. On behalf of the Ports Management team, we want to thank Florent for his years of service, he will be missed. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/08/23/change-in-the-freebsd-ports-management-team/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] FreeBSD 9.1 ports feature freeze
The FreeBSD 9.1 schedule has been published, http://www.freebsd.org/releases/9.1R/schedule.html. Historically we have done a Feature Freeze at RC1, we are going to try do it with RC2 this time, tentatively scheduled for August 3, subject to schedule slippage. At the time the the Release Engineering team announces RC2 is ready, we will then enforce "Feature Safe" commits only. This means no sweeping changes will be allowed, see http://www.freebsd.org/portmgr/implementation.html#sweeping_changes Once portmgr@ is satisfied that the requisite packages are built to ship with FreeBSD 9.1, the ports tree will be re-opened for business. Thomas on behalf of portmgr http://blogs.freebsdish.org/portmgr/2012/07/25/freebsd-9-1-ports-feature-freeze/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[HEADS UP] Ports tree has been migrated to Subversion
The migration to Subversion is done and the SVN->CVS exporter is running. Before committing please read the Ports Subversion Primer, http://wiki.freebsd.org/PortsSubversionPrimer. Please feel to add missing parts of fix it if something is wrong. For those who like to mirror the repository, the svn mirror seed will be available in /pub/FreeBSD/development/subversion/ on a mirror near you. First places it will likely be are http://freebsd.isc.org/pub/FreeBSD/development/subversion/ and http://ftp.dk.freebsd.org/pub/FreeBSD/development/subversion/. Be aware that the uncompressed repository is about 14GB. Many thanks to simon@ for all the work he did this weekend to make the switch happen! http://blogs.freebsdish.org/portmgr/2012/07/16/ports-tree-has-been-migrated-to-subversion/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Ports tree migration to Subversion
On Sun, Jul 08, 2012 at 08:59:08PM +0100, Anton Shterenlikht wrote: > On Wed, Jun 27, 2012 at 05:30:11PM +0000, Thomas Abthorpe wrote: > > The FreeBSD ports tree will migrate from CVS to Subversion soon. The > > anticipated date for the migration is July 14th. This will have no impact > > for ports tree users as there will be a SVN to CVS exporter. > > > > Please note that cvsup will still work after the migration. Nevertheless > > c(v)sup is pretty dated so you may want to see if portsnap(8) will fit your > > needs. > > Will it be possible to use subversion directly? Yes, absolutely, there will be a means to do checkouts over http, just as we have available for src and docs, unfortunately, I do not have the details available to me at this moment. > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpcjfok5Oy9G.pgp Description: PGP signature
[HEADS UP] Ports tree migration to Subversion
The FreeBSD ports tree will migrate from CVS to Subversion soon. The anticipated date for the migration is July 14th. This will have no impact for ports tree users as there will be a SVN to CVS exporter. Please note that cvsup will still work after the migration. Nevertheless c(v)sup is pretty dated so you may want to see if portsnap(8) will fit your needs. Beat and Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/06/27/ports-tree-migration-to-subversion/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: someone broke bsd.port.mk ?
On Fri, Jun 08, 2012 at 04:08:49PM -0400, Michael Scheidell wrote:
>
>
> On 6/8/12 3:55 PM, Jakub Lach wrote:
> > "/usr/ports/Mk/bsd.port.mk", line 6097: Malformed conditional
> > (${_COMPLETE_OPTIONS_LIST:O} != ${_FILE_COMPLETE_OPTIONS_LIST:O})
> >
> > Fresh portsnap, some there were changes to bsd.port.mk..
> >
> > --
> > View this message in context:
> > http://freebsd.1045724.n5.nabble.com/someone-broke-bsd-port-mk-tp5716638.html
> > Sent from the freebsd-ports mailing list archive at Nabble.com.
> > ___
> > freebsd-ports@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
> correct, looks broken:
>
> see my email of a few mins ago:
>
>
>
> Original Message
> Subject: woops: Re: conditional config is skipped for optionsNG'ified
> ports
> Date: Fri, 8 Jun 2012 15:28:04 -0400
> From: Michael Scheidell
> Organization: SECNAP Network Security Corp
> To:
>
>
>
> On 6/8/12 2:44 PM, Baptiste Daroussin wrote:
> > Should be fixed thank you. Bapt
> old one worked on devel/cross-gcc
> pcvs co -r 1.725 ports/Mk/bsd.port.mk
>
> make TGTARCH=arm TGTABI=elf clean
> ===> Cleaning for arm-elf-gcc-4.5.2
>
> this newest one, not so much:
>
> $FreeBSD: ports/Mk/bsd.port.mk,v 1.726 2012/06/08 18:44:17 bapt Exp $
>
> make TGTARCH=arm TGTABI=elf clean
> "/usr/ports/Mk/bsd.port.mk", line 6097: Malformed conditional
> (${_COMPLETE_OPTIONS_LIST:O} != ${_FILE_COMPLETE_OPTIONS_LIST:O})
> "/usr/ports/Mk/bsd.port.mk", line 6429: if-less endif
> make: fatal errors encountered -- cannot continue
>
>
> --
> Michael Scheidell, CTO
> >*| * SECNAP Network Security Corporation
> d: +1.561.948.2259
> w: http://people.freebsd.org/~scheidell
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
A fix was committed that appears to have address the situation, please
update your ports tree and give it a try to verify the changes work for
you.
Thanks!
Thomas
--
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe
pgp60KzHxef8y.pgp
Description: PGP signature
[HEADS UP] Upcoming ports feature freeze
FreeBSD 8.3 RC1 has been pulicly announced, it is now time for the the Ports Feature Freeze. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval, but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date. Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2012/03/09/ports-feature-freeze-for-freebsd-8-3-is-now-in-effect/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Upcoming ports feature freeze
On Sun, Feb 19, 2012 at 10:16:45PM +, Thomas Abthorpe wrote: > The FreeBSD 8.3 release process is under way, you can view the schedule, > http://wiki.freebsd.org/Releng/8.3TODO > > As has become the custom, a ports feature freeze is anticipated to be > announced with the RC1 date, tentatively scheduled at this time > for March 2, 2012. Watch for further announcements as we get closer. > > During the feature freeze, committers are expected to be conservative with > their commits, that is, no sweeping commits, infrastructure changes, or > commits to ports with a high number of dependencies. > I said I would follow up as we got closer, and so here it is, finally. We will flip the switch for Feature Freeze after the announcement for RC1 officially goes out. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpq0CKnBIPOX.pgp Description: PGP signature
Re: MASTER_SITE_FEDORA_LINUX in bsd.sites.mk
On Wed, Jan 18, 2012 at 04:27:47PM -0600, Mark Linimon wrote: > On Wed, Jan 18, 2012 at 09:09:10PM +, Chris Rees wrote: > > I worry about the ethics of 'stealing' Fedora's bandwidth with other > > people's ports; we should only be using their mirrors if it's explicitly > > developed by Fedora. > > Correct. dougb has pointed this out before and no one has taken the > cycles to go act on it. Consider this a task that needs volunteers. > > (A similiar caveat applies to the Debian and NetBSD sites; I believe > it was Debian he flagged previously.) > > mcl I have engaged the mirror maintainers and infrastructure people at Gentoo and Debian on this matter, and for the sake of completeness our own FreeBSD mirror admins. The short response is, "That is fine, just do it". Yay, there was much rejoicing in the land, end of story :) The longer part of this, is that we are all opensource-minded people, publicly sharing has been a part of our genetics since inception. It is ok to ustilise the public facing mirrors, just please do not abuse them. Another common thread I got from the maintainers that contacted me back was that they mirror for multiple projects on their site anyway, and that the additional traffic was nominal at best. One fellow told me he was in active competition for throughput with another mirror, and welcomed the extra hits he was getting. Through all of this, I was asked, particularly by the Debian folks, please ask permission of mirror maintainer before you list their mirror in the master list. You will see my recent commit to bsd.sites.mk, I added 4 more volunteers to the Debian list, http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.sites.mk.diff?r1=1.558;r2=1.559 I hope this helps clarify the usage of other project mirrors. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp2MQKxgZyST.pgp Description: PGP signature
[HEADS UP] Upcoming ports feature freeze
The FreeBSD 8.3 release process is under way, you can view the schedule, http://wiki.freebsd.org/Releng/8.3TODO As has become the custom, a ports feature freeze is anticipated to be announced with the RC1 date, tentatively scheduled at this time for March 2, 2012. Watch for further announcements as we get closer. During the feature freeze, committers are expected to be conservative with their commits, that is, no sweeping commits, infrastructure changes, or commits to ports with a high number of dependencies. http://blogs.freebsdish.org/portmgr/2012/02/19/upcoming-8-3-ports-feature-freeze ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Ports slush for FreeBSD 9.0 is officially over
Sorry folks, sent this out a week ago via other channels, and seemed to get gobbled up along the way Just to make it officially official, now that FreeBSD 9.0 has been shipped, the ports slush state is now been lifted. Ports committers are now entitled to perform sweeping commits. Keep in mind that -exp runs are always a good idea if you think there is a significant change to the ports tree. And just remember, PLEASE TRY TO NOT BREAK THE INDEX! Thomas on behalf of portmgr@ -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpwzwEZUm4Et.pgp Description: PGP signature
Re: New mailing list for ports announcements
On Thu, Dec 29, 2011 at 11:19:00AM +0400, Yuri Pankov wrote: > On Thu, Dec 29, 2011 at 09:23:05AM +0300, Sergey V. Dyatko wrote: > > On Thu, 29 Dec 2011 00:59:26 -0500 > > Thomas Abthorpe wrote: > > > > > At the request of adamw@ (and others) we have setup a ports-announce@ > > > mailing list to try distinguish the usual traffic on the ports@ list > > > vs the announcements that seem to get lost in there. > > > > > > > Useless and harmful list, IMO. People who can 'lost' announcements here > > likely lose it on another list, but there is a chance that people who > > read ports@ lose announce/CFT from _only_ freebsd-ports-announce. > > Of course, you can write to multiple lists.. But lets look at current@ > > stable@ and performance@ archives... > > tadam! "Benchmark (Phoronix): FreeBSD 9.0-RC2 vs. Oracle Linux 6.1 > > Server". > > You seem to miss the "moderated" part.. Thank you, Yuri As implied, but not necessarily stated, moderated and not intended for discussions. Discussion are welcome in this forum, as always. > > > Is that ok ? I think 'No' ( Tons of spam in [ 3 of N ] ML that I > > subscribed ) > > > > > You can subscribe at > > > http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce > > > > > > It is intended, but not limited, to be a means of communicating > > > portmgr@ announcements, Calls for Testing, plus other relevant > > > information to be used by our committers and ports maintainer > > > community. > > > > > > It is our hope to keep this relatively low in traffic. It is a > > > moderated list, under the auspices of portmgr@. > ^ > > > > > > Please subscribe sit back, and enjoy. > > > Yuri Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp7n7RfKbueq.pgp Description: PGP signature
New mailing list for ports announcements
At the request of adamw@ (and others) we have setup a ports-announce@ mailing list to try distinguish the usual traffic on the ports@ list vs the announcements that seem to get lost in there. You can subscribe at http://lists.freebsd.org/mailman/listinfo/freebsd-ports-announce It is intended, but not limited, to be a means of communicating portmgr@ announcements, Calls for Testing, plus other relevant information to be used by our committers and ports maintainer community. It is our hope to keep this relatively low in traffic. It is a moderated list, under the auspices of portmgr@. Please subscribe sit back, and enjoy. Thomas on behalf of portmgr@ -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpWZs5N11LSs.pgp Description: PGP signature
Re: More lame portmgr poetry
On Fri, Dec 23, 2011 at 08:46:06PM -0500, Glen Barber wrote: > On Fri, Dec 23, 2011 at 07:42:19PM -0500, Eitan Adler wrote: > > On Fri, Dec 23, 2011 at 4:45 PM, Glen Barber wrote: > > > Hmm.. Why does portmgr get to have all the fun? :) > > > > Do we get to hear you both sing at this year's BSDCAN? > > I'm quite certain none of us want that. > > Glen > +1 I can't speak for Glen per se, but a chorus of chain saws sound better than my singing :) Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpf0o46FewrL.pgp Description: PGP signature
More lame portmgr poetry
Blame it on Me with apologies to the Barenaked Ladies Here we are again and we're looking at each other as if the other is to blame You think you're so smart, but you broke the INDEX, and you'll probably break it again portmgr@ told you not to do it, but if you do, what can be gained? If all else fails, you can blame it on me. If all else fails you can blame it on me. If all else fails you can blame it on me. If all else fails blame it on me. If all else fails you can blame it on me. Then you smile again but you're looking at me as if there's something I'm supposed to say. Forgive me portmgr@, I've committed enough, and that's all I can do today Maybe if you'd ask me on any other given day I wouldn't have time for you or anything that you say but it's alright now, you can blame it on me. If all else fails you can blame it on me. If all else fails you can blame it on me. If all else fails blame it on me. If all else fails you can blame it on me. Yes ports tree I love you, but sometimes I think my time is not enough for you So you say you can fix it? Well that's fine, go ahead, la la la I can't hear you. There you are, the repository is half a continent away; I wax poetic as your breaking portsnap, If all else fails you can blame it on me. If all else fails you can blame it on me. If all else fails blame it on me. If all else fails you can blame it on me. -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpt0eUm7sUMS.pgp Description: PGP signature
Re: snort error install [bug report]
On Fri, Dec 16, 2011 at 04:47:04PM +0400, Alex wrote: > Hello! > > When I install snort-2.9.2 from the ports have a problem. > > > See below (copy from shell): > > "Making install in etc > Making install in templates > Making install in contrib > Making install in rpm > Making install in schemas > Making install in m4 > Making install in preproc_rules > Making install in tools > Making install in u2boat > test -z "/usr/local/bin" || ../.././install-sh -c -d > "/usr/local/bin" >/bin/sh /usr/local/bin/libtool --mode=install install > -s -o root -g wheel -m 555 u2boat '/usr/local/bin' > libtool: install: install -o root -g wheel -m 555 -s > u2boat /usr/local/bin/u2boat > test -z "/usr/local/share/doc/snort" || ../.././install-sh > -c -d "/usr/local/share/doc/snort" > install -o root -g wheel -m 444 README.u2boat > '/usr/local/share/doc/snort' > Making install in u2spewfoo > test -z "/usr/local/bin" || ../.././install-sh -c -d > "/usr/local/bin" >/bin/sh /usr/local/bin/libtool --mode=install install > -s -o root -g wheel -m 555 u2spewfoo '/usr/local/bin' > libtool: install: install -o root -g wheel -m 555 -s > u2spewfoo /usr/local/bin/u2spewfoo > test -z "/usr/local/man/man8" || ./install-sh -c -d > "/usr/local/man/man8" > install -o root -g wheel -m 444 snort.8 > '/usr/local/man/man8' > test -z "/usr/local/lib/pkgconfig" || ./install-sh -c -d > "/usr/local/lib/pkgconfig" > install -o root -g wheel -m 444 snort.pc > '/usr/local/lib/pkgconfig' > ===> Installing rc.d startup script(s) > # mss: only doing this because snortsam patch/autojunk > messes up paths > # life is too short to figure out why. > rmdir: /usr/local/lib/pkgconfig: Directory not empty > *** Error code 1 > > Stop in /usr/ports/security/snort. > *** Error code 1 > > Stop in /usr/ports/security/snort. > " > --- > Professional hosting for everyone - http://www.host.ru This can be better addressed if you contact the maintainer directly, z...@freebsd.org Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpbpal1KdanA.pgp Description: PGP signature
Please welcome beat@ to portmgr@
We are pleased to announce the addition of Beat Gaetzi (beat@) to the team. Beat, like many others was a long time contributor prior to receiving his commit bit in 2009. Beat is well know for his work with the Gecko and Vbox teams, in addition to his hosting of test/development repositories for many of our community members. Beat's next unenviable task will be taking us through the rocky road ahead in migrating the CVS Ports repository to Subversion. Please join me in welcoming Beat to the team. Congratulations Beat! Thomas on behalf of portmgr@ http://blogs.freebsdish.org/portmgr/2011/12/02/please-welcome-beat-gaetzi-to-the-ports-management-team/ -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpirv26iRVxF.pgp Description: PGP signature
Feature freeze for 9.0 is now in effect
With this commit, http://svnweb.freebsd.org/base?view=revision&revision=227337, the RC2 phase is under way. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval, but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date. Thomas on behalf of portmgr@ -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpnH6YKuiaR2.pgp Description: PGP signature
New member for portmgr@
Hey all! Just wanted to say that I have been made a voting member of portmgr@ http://blogs.freebsdish.org/portmgr/2011/03/10/new-member-for-portmgr/ Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpUzfso3k4Gi.pgp Description: PGP signature
Re: www/chromium MAINTAINER, was Re: chromium producing constant hdd access
On Tue, Jan 18, 2011 at 01:13:19PM +0100, Julian H. Stacey wrote: > Hi, > Reference: > > From: Mark Linimon > > Date: Tue, 18 Jan 2011 00:48:50 + > > Message-id: <20110118004850.gb17...@lonesome.com> > > Mark Linimon wrote: > > On Mon, Jan 17, 2011 at 08:12:40PM +0100, Julian H. Stacey wrote: > > > rene@ has ignored request to roll back. If rene@ resigns, > > > MAINTAINER would revert to po...@freebsd.org so others could fix > > > FreeBSD's current ports/www/chromium > > > > Because of the legal questions surrounding chromium, > > I know nothing of that. Just that a month ago it compiled, now it won't. > > > portmgr will ensure > > that it does not revert to ports@ :-) > > mcl > > So how about: > Revert to something that will compile, with no MAINTAINER. > Or delete port ? > A port that > - wont build, > - the maintainer won't fix, > - has security issues, > - is legaly problematic > - ports@ is scared of inheriting > - that we can't fix by adding a _DEPENDS etc > seems a waste of time & name space, > > Cheers, > Julian I suggest you subscribe to http://lists.freebsd.org/mailman/listinfo/freebsd-chromium, and make make your intentions known about what you can do to assist in getting a more current version of Chromium tested, built and updated in ports. Porting a browser as complex as Chromium is a lot of work, takes a lot of time, and requires a lot of attention to detail. A small group of us has been assisting Rene for a while now, and we have decided it is now time to grow a FreeBSD Chromium Community. Within this community we are hoping to find testers, coders, helpers, coders, people with a general interest in Chromium, and did I mention coders? So please subscribe, make your inquiries, and as people come on board, we will be able to do more to spread the word about Chromium for FreeBSD. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpHzuY6hcX5X.pgp Description: PGP signature
[HEADS UP] Ports feature freeze to come into effect
With this commit, http://svn.freebsd.org/changeset/base/217255, the RC2 phase is under way. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date. Thomas on behalf of portmgr@ -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpcwYrev2ruh.pgp Description: PGP signature
Upcoming Feature Freeze
In preparation for 7.4/8.2-FreeBSD, the ports tree will be in feature freeze after Release Candidate 2 (RC2) is released, tentatively planned for January 7, 2011. If you have any commits with high impact planned, get them in the tree before then and if they require an experimental build, have a request for one in portmgr@ hands within the week or so. Note that this again will be a feature freeze and not a full freeze. Normal upgrade, new ports, and changes that only affect other branches will be allowed without prior approval but with the extra Feature safe: yes tag in the commit message. Any commit that is sweeping, i.e. touches a large number of ports, infrastructural changes, commits to ports with unusually high number of dependencies, and any other commit that requires the rebuilding of many packages will not be allowed without prior explicit approval from portmgr@ after that date. Thomas with portmgr-secretary@ hat on -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpHOhRQgAaH8.pgp Description: PGP signature
Things all ports mentors and potential mentees should know
ops and grows, the mentee may be granted "implicit"
commit rights. This can include trivial changes to a Makefile, pkg-descr
etc. Similarly, it may include PORTVERSION updates that do not include
plist changes. Other circumstances may be formulated at the discretion
of the Mentor. However, during the period of mentorship, a port version
bump, that affects dependent ports should be checked by a mentor.
- Just as we are all varied individuals, each mentee has different learning
curves, time commitments, and other influencing factors that will
contribute to the time required before they can fly solo. Empirically, a
mentee should be observed for at least 3 months. 90-100 commits is
another target that a mentor could use before releasing a mentee. Other
factors to consider prior releasing a mentee, is the number of mistakes
they may have made, QATs received etc. If they are still making rookie
mistakes, they still require mentor guidance.
Mentor/Co-Mentor debate
---
- When a request gets to portmgr@, it usually reads as, "I propose 'foo' for
a ports commit bit, I will co-mentor with 'bar'". Proposal received, voted,
and carried.
- The mentor is the primary point of contact or the "first among equals",
the co-mentor is the backup.
- Some reprobate, whose name shall be withheld, made this commit
http://lists.freebsd.org/pipermail/cvs-ports/2007-September/134614.html,
it seems to be the first one documented in the ports tree, until somebody
can prove otherwise. Similar co-mentor commits have also been spotted in
the src tree. Does this make it right? Does this make it wrong? It seems
to be part of the evolution of how things are done.
Expectations
- We expect mentees to be prepared for constructive criticism from the
community. There's still a lot of "lore" that isn't written down.
Responding well to constructive criticism is what we hope we are
selecting for by first reviewing their existing contributions on IRC and
mailing lists.
- We warn mentees that some of the criticism they receive may be less
"constructive" than others, (whether through language communication
problems, or excessive nit-picking), and that dealing with this
gracefully is just part of being in a large community. In case of
specific problems with specific people, or any questions, we hope that
they will approach a portmgr@ member on IRC or by email.
Supplementary Reading
=
- http://www.freebsd.org/doc/en/articles/committers-guide - The FreeBSD
Committer's Guide
- http://www.freebsd.org/doc/en/articles/contributing-ports - Contributing
to the FreeBSD Ports Collection
- http://www.freebsd.org/doc/en/books/porters-handbook - FreeBSD Porter's
Handbook
Summary
===
The thing to keep in mind is that the twin goals are to have an effective
and useful Ports Collection, with the minimum degree of interpersonal
friction, and all the while keeping in mind that this is a completely
volunteer effort, and as such is supposed to be (to some degree) fun ...
Last edited : $Date: 2010/11/27 18:36:53 $
--
Copyright 2010, The FreeBSD Portmgr Team. All rights reserved.
Redistribution, publication, translation and use, with or
without modification, in full or in excerpt, in any form or
format of this document are permitted. Excerpts must be
quoted in context and may not misconstrue the original
meaning.
http://people.freebsd.org/~portmgr/mentor_guidelines.txt.asc
--
Thomas Abthorpe | FreeBSD Committer
tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe
pgp2ylJXP75kK.pgp
Description: PGP signature
MD5 for distinfo has been deprecated
Greetings list erwin@ committed http://www.freebsd.org/cgi/query-pr.cgi?pr=149657, based on work by dougb@ and r...@. It deprecates the use of md5 checksums in distinfo. So here on in, when you run make makesum, the md5 will no longer be generated, only the sha256 checksum. Existing distinfo containing md5 info will silently be ignored. So at this time there is no need re-create distinfo for the sake of removing it, just allow the regular flow of ports updates take care of it. Thomas with portmgr-secretary@ hat on -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpZOcXZnEgUY.pgp Description: PGP signature
Happy Release Time, Freeze is over
This is my third installment of portmgr poetry triology. I have nothing else composed, yet, but who is to say what will come up for next release cycle, FEAR! Happy Release Time, Freeze is over with apologies to John Lennon So this is release time And what have you done Another version released And a new one has just begun So this is release time I hope you have fun The near and the dear one The old and the young A new version of FreeBSD has been released this year Let's hope it is a good one Without any fear And so this is FreeBSD For i386 and for amd64 For ARM and sparc64 The make world can be built And so it has been released For MIPS and for pc98 For sun4v and ia64 Let's all celebrate A new version of FreeBSD has been released this year Let's hope it is a good one Without any fear So this is release time And what have we done Another version released And a new one has just begun So this is release time I hope we had fun The near and the dear one The old and the young A new version of FreeBSD has been released this year Let's hope it is a good one Without any fear Freeze is over, if you want it Freeze is over now -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpMFDQjR5ZQB.pgp Description: PGP signature
Give freeze a chance
The next wave of the challenge, fear, there is one more already composed to be released with 8.1! -- Give Freeze a chance with apologies to John Lennon et al Ev'rybody's talkin' 'bout portism, srcism, docism, cvsism, svnism, tagism This-ism, that-ism, ism ism ism All we are saying is give freeze a chance All we are saying is give freeze a chance C'mon Ev'rybody's talkin' 'bout re@, core@, doceng@, donations@, secteam@, marketing@, portmgr@, vendor-relations@ All we are saying is give freeze a chance All we are saying is give freeze a chance Let me tell you now Ev'rybody's talkin' 'bout Revolution, evolution, i18n, l10n, documentation, Integration, administration, applications, congratulations All we are saying is give freeze a chance All we are saying is give freeze a chance Ev'rybody's talkin' 'bout Erwin Lansing, Mark Linimon, Martin Wilke, Pav Lucistnik, Florent Thoumie, Ion-Mihai Tetcu, Kris Kennaway, Joe Marcus Clarke, Thomas Abthorpe too All we are saying is give freeze a chance All we are saying is give freeze a chance Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgp8iMaxaczCs.pgp Description: PGP signature
Re: kdebase3 - CVE-2010-0436
Thanks for the patches, we will look at it as soon as our time permits Thomas On 25/04/2010, Oliver Pinter wrote: > this errata is fixed in kde4 and not yet in kde3 @ports... > > -- Forwarded message -- > From: Oliver Pinter > Date: Sun, 25 Apr 2010 00:31:03 +0200 > Subject: kdebase3 - CVE-2010-0436 > To: k...@freebsd.org > > hi all! > > some RH patches for cve-2010-0436: > > final: https://bugzilla.redhat.com/attachment.cgi?id=400244&action=diff > (I think this for kde4, it depend on cmake) > v1/1: https://bugzilla.redhat.com/attachment.cgi?id=401213&action=diff > v1/2: https://bugzilla.redhat.com/attachment.cgi?id=401214&action=diff > > and attached patch for kdm-kde3 from Red Hat kdebase3 source > -- Thomas Abthorpe, FreeBSD Ports Committer tabtho...@freebsd.org, http://people.freebsd.org/~tabthorpe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: drop devel/allegro and devel/allegro-devel
On Mon, Apr 19, 2010 at 08:49:10AM -0400, Naram Qashat wrote: > On 04/19/10 04:16, Eitan Adler wrote: > > Since I no longer use allegro and don't have time to update them I'd > > like to drop maintainership of allegro. > > > > If anyone would like to take them feel free... > > > > Note to the next maintainer: devel/allegro needs to be updated to > > 4.4.1.1 and devel/allegro-devel needs to be updated to 4.9.19. > > I'll take up maintaining both these ports. > > Naram Qashat Transferred :) Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpJ8ttEyDLJa.pgp Description: PGP signature
Re: Responding to a challenge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 20 Apr 2010 16:29:57 -0400 Diane Bruce wrote: > Pity! I was going to suggest it would be worth a buck a piece for > developers to witness you singing, all proceeds to the FreeBSD > foundation. ;-) My singing would be easy to emulate, bring a chain saw, and fire it up!!! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvOY7cACgkQ5Gm/jNBp8qDwjQCfRbI60dd6aUzhjwbWHzyReqa2 m3AAn2HPd/dE6Paw0x6xT6KlIL5/0Zu6 =NqVx -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Responding to a challenge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 20 Apr 2010 14:25:58 -0400 Diane Bruce wrote: > On Tue, Apr 20, 2010 at 09:39:17PM +0400, Max Brazhnikov wrote: > > On Sun, 18 Apr 2010 23:52:43 -0400, Thomas Abthorpe wrote: > > > edwin@ threw down this gauntlet when I accepted my recent hat, > > > http://blogs.freebsdish.org/tabthorpe/2010/03/25/catching-up-on-recent-even > > > ts/comment-page-1/#comment-13022 > > > > > > I have responded. Sure it is lame, I am a porter, not a song writer! > > > > Great! We are waiting for audio version now! :) > > How about you two sing a duet at BSDCAN? > > - Diane Sadly my band is trapped in Europe, and I am personally unable to travel at this time, and will not be at BSDCan this year :( Maybe next year! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkvN+vIACgkQ5Gm/jNBp8qB9igCeI6MjHdtB/WHDQIlLm/vL8p9i O0oAn2ce2syVx8ZXdFA+OdEzBDvMjtZv =7sIU -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Responding to a challenge
edwin@ threw down this gauntlet when I accepted my recent hat, http://blogs.freebsdish.org/tabthorpe/2010/03/25/catching-up-on-recent-events/comment-page-1/#comment-13022 I have responded. Sure it is lame, I am a porter, not a song writer! --- Something to Port with apologies to Queen Can anybody find me something to port? Each morning I get up looking at GNATS Can barely believe what I see Take a look on the mailing lists People, what are you doing to me? I have spent all these years closing PRs But I just can't get no relief! Somebody, somebody Can anybody find me something to port? I work hard, working on ports I work until my brain hurts At the end of the day, I queue up my last job And I try to get some sleep Until I realise I didn't sync my tree Oh, somebody, somebody Can anybody find me something to port? (He works hard) Everyday, I try and I try and I try But the PRs keep on coming in My family thinks I am crazy The say, "You do this for free?" The say I need a new hobby Got no common sense I got nobody who understands me Yeah, yeah, yeah, yeah Oh, somebody, somebody Can anybody find me something to port? Got not feel, keep losing more sleep I just keep drinking more tea I'm ok, I'm alright Ain't gonna let them beat me I just gotta get out of this jail(8) Someday I'm gonna be free! Find me something to port Can anybody find me something to port? -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe pgpyfuzB0bP6J.pgp Description: PGP signature
Re: New portmgr secretary: Thomas Abthorpe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 19 Mar 2010 10:27:45 -0400 Greg Larkin wrote: > Congratulations, Thomas, for a well-deserved accolade! I appreciate your > multi-faceted contributions to the project, especially mentoring so many > new committers. > > Best regards, > Greg Thanks, Greg :) - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkukN0gACgkQ5Gm/jNBp8qBZfQCfe86Ttq5PINgJ1V2Hz+IafoKH MS8An2mlnGBCGYgizvQAeZfcwMfgvQa3 =Na6e -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: New portmgr secretary: Thomas Abthorpe
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 18 Mar 2010 13:34:24 -0300 Marcelo wrote: > Congrats. Thanks :) - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuiVzwACgkQ5Gm/jNBp8qCeWgCfRIVYgem2FxZqpYzuj4HHhV4t kbAAnAiZYL7qDjiGVPYuNZHb0qBt4bLZ =+iBD -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: qt33 plist errors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 16 Feb 2010 05:52:08 + "Philip M. Gollucci" wrote: > http://tb.p6m7g8.net//errors/9-CURRENT-amd64-snmp/qt-3.3.8_11.log > > See near the bottom, any else get this ? I have done a sampling of builds across various platforms, all build clean. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkuEkHUACgkQ5Gm/jNBp8qCt/gCghhZzqIY0AEpFpF147TqDasO5 csYAnRHnVjS/YokhBcKcm/mfFKnLEipz =hXe7 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Delete a port I maintain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 07 October 2009 05:15:00 Eitan Adler wrote: > The upstream author no longer maintains this port and I don't have the > time to fix it. > This port could be removed from the ports tree. > > portname: hebrew/geresh > broken because: needs update for the new fribidi paragraph API > build errors: > http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2009081417/iw > -geresh-0.6.3_1.log (_Aug_23_08:41:05_UTC_2009) > overview: > http://portsmon.FreeBSD.org/portoverview.py?category=hebrew&portname=ge > resh > Done PRs are preferred :) Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkrN4GkACgkQ5Gm/jNBp8qB3nACfThipxycOY4HPdD4abR6Msgpy zXYAn0wQHlUmB9pF5qk95DcwtLzfMrLv =eCSV -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[CFT] Qt-4.6.0 technology preview ready for beta test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The FreeBSD KDE team is pleased to announce the first public call to test Qt-4.6.0-tp1. It can downloaded from the area51 repo with the following command svn co http://area51.pcbsd.org/branches/qt-4.6tp/ - From there you can use kdemerge to overlay the changes to your ports tree. Please note that you will require some patches from the repo to get games/kdegames4 and net/kdenetwork4 to build. Our initial testing has yielded a binary compatibility between 4.6.0 and 4.5.2. Please be aware that this needs more testing. One other warning, the py-qt* bindings are still a work in progress. Dima Panov, aka fluffy@, is currently working on it. Please send feedback to kde-free...@kde.org. This branch was made possible by the hard work of Alberto Villa and other contributors. - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkq9qHIACgkQ5Gm/jNBp8qCaFgCfbby4zu5q/KsEHB2S3sIoE0VO +gkAn1qpbMt1n7Oqx8LJmaynUjRfEqeb =HX4f -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: squirrelmail port
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On September 1, 2009 07:36:56 am Johan Hendriks wrote: > Since when are we using release candidate's of squirrelmail in the ports > tree. > I think we need an devel port for that so that we can use the stable > squirrelmail port as stable, and use the devel port if we want to use > beta's and release candidates. > > > > Regards, > Johan > Hey Johan Once the XSS vulnerability was brought to my attention, http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2964 (plus related links) I decided to err on the side of caution, and upgrade to a more stable version, albeit an RC. Yes I know I could have patched it, but chose not to. I am hoping that the release branch will be out sooner than later. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqdHgkACgkQ5Gm/jNBp8qAeRwCeInu4BpN9IWQMa+0glxhFJz0B exIAnRChCLMGSRWHPvOT86aMIHsfUI8l =YoJH -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: May I commit your ports to fix the hardcore?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On July 2, 2009 03:30:46 pm Jeremy Messenger wrote: > May I commit your ports to fix the hardcore of ltmain.sh and libtool? Here > are the patches: > > kde@: http://people.freebsd.org/~mezz/diff/kdeutils3.diff Hi Jeremey Feel free to commit the patch. :) Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpNEPAACgkQ5Gm/jNBp8qCxHQCeIPfcfgQvgWfufaA5mYtodXKB CjEAn3/PjPsis/Gy1kCWRZnNHnxlh2Fs =amc/ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
Should the category come to being, all self identified ports will remain in their original folder, and have CATEGORIES extended to include the new name. Thomas On 26/06/2009, Carlos A. M. dos Santos wrote: > On Fri, Jun 26, 2009 at 5:10 PM, Thomas Abthorpe > wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On June 25, 2009 08:51:43 pm Carlos A. M. dos Santos wrote: >>> Guys, you have been discussing the category *name* for eight days now >>> without reaching a consensus. This is becoming somewhat boring. Please >>> do not reinvent the wheel. Whether you like it or not, i18n is a well >>> established and widely accepted acronym. >> >> Here endeth the debate >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=136072 >> >> - From here it is yay or nay. > > Thanks. You might also want to move the portuguese/*[il]1[08]n* ports > to the new category. > > -- > My preferred quotation of Robert Louis Stevenson is "You cannot > make an omelette without breaking eggs". Not because I like the > omelettes, but because I like the sound of eggs being broken. > -- Sent from my mobile device Thomas Abthorpe, FreeBSD Ports Committer tabtho...@freebsd.org, http://people.freebsd.org/~tabthorpe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 25, 2009 08:51:43 pm Carlos A. M. dos Santos wrote: > Guys, you have been discussing the category *name* for eight days now > without reaching a consensus. This is becoming somewhat boring. Please > do not reinvent the wheel. Whether you like it or not, i18n is a well > established and widely accepted acronym. Here endeth the debate http://www.freebsd.org/cgi/query-pr.cgi?pr=136072 - From here it is yay or nay. - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpFK1oACgkQ5Gm/jNBp8qA/3wCePZ4JOFZkKT5lm0ffq1cCQGvi FdIAn3ZnbGUVoumcwmxfVpVwBWVQVBDe =Qko5 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
Friday will be one week for the topic, at which point I will take on the next leg of the battle, which is making the pitch to portmgr. Thomas On 25/06/2009, Mark Foster wrote: > per...@pluto.rain.com wrote: >>>> If i18n is too cryptic or too alphanumeric, and >>>> internationalization is too long, why not go with "nls"? >>>> >>> I personally think that nls is equally as cryptic as i18n or l10n. >>> >> >> Anyone care for "intlzn"? It's short, should still tab-complete >> from "in", and it may be a bit less cryptic than nls, i18n, or l10n. >> > If I may be so bold as to present a democratic outcome. > To help settle the matter please vote on this issue within 48 hours. > <http://www.micropoll.com/akira/mpview/615850-178803> > > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Sent from my mobile device Thomas Abthorpe, FreeBSD Ports Committer tabtho...@freebsd.org, http://people.freebsd.org/~tabthorpe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 24, 2009 02:24:01 pm Charlie Kester wrote: > >On June 23, 2009 04:36:08 pm Charlie Kester wrote: > >> On Tue 23 Jun 2009 at 12:05:55 PDT Thomas Abthorpe wrote: > >> >Localization is a subset Internationalization, so the new category > >> >becomes a catch all for both entities. > >> > >> If i18n is too cryptic or too alphanumeric, and internationalization is > >> too long, why not go with "nls"? > > > >I personally think that nls is equally as cryptic as i18n or l10n. > > But it has the virtue of being purely alphabetic. and thus meets one of > the objections that have been raised. > > I don't put much weight on the "cryptic" argument myself. I expect that > anyone who is doing internationalization work is familiar with all of > these terms -- and if not, they need to *make* themselves familiar with > them. ack ack, point well taken. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpCdBsACgkQ5Gm/jNBp8qBZDQCdHDTLXYsYKyK4FXo0xL9VRfdT lIAAnRTOr2q4jkUtiMKwRW7q/0ARTrCT =Sy7h -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 23, 2009 05:35:16 pm Tim Bishop wrote: > > If i18n is too cryptic or too alphanumeric, and internationalization is > > too long, why not go with "nls"? > > How about internationalisation? ;-) > > Tim. As a Canadian who prefers en_GB, I fought every urge to propose that one. Since FreeBSD has en_US as its base language, I felt compelled to use zed in of ess :> Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpCMTQACgkQ5Gm/jNBp8qB+PQCfaNgQ5OT8BMBUwkr+0c+Gt/Io uq4AmgJS948BR3k4oAdocfExMibWrOuq =rMR7 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 23, 2009 04:36:08 pm Charlie Kester wrote: > On Tue 23 Jun 2009 at 12:05:55 PDT Thomas Abthorpe wrote: > >Localization is a subset Internationalization, so the new category > >becomes a catch all for both entities. > > If i18n is too cryptic or too alphanumeric, and internationalization is > too long, why not go with "nls"? I personally think that nls is equally as cryptic as i18n or l10n. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpCMHoACgkQ5Gm/jNBp8qCQNACdEtpDr3bmOoZAW5dHBWKcdotn xPQAn1LGRsg+xr/csmhFaNUXhpUFqugy =HTv2 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 23, 2009 10:27:59 pm Eitan Adler wrote: > > I would like for it to be a real category, so we can unclutter the misc/ > > folder, and encourage more local/internationalized stuff in the new > > category. > > I would like it to be a virtual category. > Lets take a random i18n port: misc/koffice-i18n-th > The port would get moved to editors/ and i18n would get added as a > virtual category. It is more organized this way. A person looking for > editors doesn't have to look in both editors/ and misc/ (or i18n/) +1 for virtual category, thanks for the feedback. - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpCL5kACgkQ5Gm/jNBp8qCBgQCcDFZOSvK6aZqwSfR2YYjSU/q1 APIAn1WALvnxuPTD/yvQdFdbN/WjBTrD =j0LU -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 23, 2009 01:52:47 pm Alexey Shuvaev wrote: > On Tue, Jun 23, 2009 at 10:13:48AM -0400, Thomas Abthorpe wrote: > > 2009/6/23 Chris Rees : > > > 2009/6/23 Doug Barton : > > >> Thomas Abthorpe wrote: > > >>> To have localization, you need internationalization, so from this, I > > >>> stand by my original proposal of i18n. > > >> > > >> I have no objection to your reasoning, but continue to object to the > > >> specific string. If you're going to go down this road then > > >> "internationalization" would be the better choice. > > >> > > >> Doug > > > > > > I would agree with Doug. We're in the days of tab-completion, and > > > typing 'in' will suffice to get there. I for one *hate* numbers > > > in paths; it takes one's hand off the letters. Also, I had to look up > > > i18n to find out what it was... Categories should be immediately > > > descriptive. > > Hard to achive... x11-wm, x11-fm, audio vs. multimedia, ... Agreed, but I still don't have to like it! > > > > Also, the French have to use Shift to type numbers; it's even more of > > > a pain for them! > > Unrelated problem. Agreed, FreeBSD is developed/rooted in en_US anyway. And from my limited contact with my European brethren, they seem to prefer US keyboards for their FreeBSD work. > > head -50 test.c > kill -s KILL 46129 > man 3 printf > mount /dev/da0a mnt/ > > I think you can't avoid using numbers in command-line. > BTW, numbers are much better than spaces or localized characters: > 'Мои документы' ( == 'My Documents') Touche! > > > > Chris > > > > You have struck a chord with numbers in the path, reminds me of the > > pre-Xorg days with /usr/X11R6, not sure what I disliked more, the > > capital letters or the numbers! > > > > I hereby relent, and yield to the logic of the arguments placed before > > me, I now agree that using internationalization for the category name > > is a better idea. > > Well, if the new category supposed to be real, > I don't like 'internationalization' name. > The reason? Very simple. > For now I get: > > ~> ls /usr/ports/ > CHANGES archivers finance misc shells > COPYRIGHT astro frenchmultimediasysutils > GIDs audio ftp net textproc > INDEX-8 benchmarksgames net-imukrainian > KNOBS biology germannet-mgmt vietnamese > LEGAL cad graphics net-p2p www > MOVED chinese hebrewnews x11 > Makefile comms hungarian packages x11-clocks > Mkconvertersirc palm x11-drivers > READMEdatabases japanese polishx11-fm > Templates deskutils java ports-mgmtx11-fonts > Tools devel koreanportuguesex11-servers > UIDs distfiles lang print x11-themes > UPDATING dns mail russian x11-toolkits > accessibility editors math science x11-wm > arabicemulators mbone security > > which fits fine in one 80x25 terminal window. > With the new category: > > ~> ls /usr/ports/ > CHANGES develnet-p2p > COPYRIGHTdistfilesnews > GIDs dns packages > INDEX-8 editors palm > KNOBSemulatorspolish > LEGALfinance ports-mgmt > MOVEDfrench portuguese > Makefile ftp print > Mk gamesrussian > README german science > Templatesgraphics security > Toolshebrew shells > UIDs hungariansysutils > UPDATING internationalization textproc > accessibilityirc ukrainian > arabic japanese vietnamese > archiversjava www > astrokorean x11 > audiolang x11-clocks > benchmarks mail x11-drivers > biology math x11-fm > cad mbonex11-fonts > chinese misc
Re: [RFC] New category proposal, i18n
2009/6/23 Chris Rees : > 2009/6/23 Doug Barton : >> Thomas Abthorpe wrote: >>> To have localization, you need internationalization, so from this, I stand >>> by >>> my original proposal of i18n. >> >> I have no objection to your reasoning, but continue to object to the >> specific string. If you're going to go down this road then >> "internationalization" would be the better choice. >> >> Doug >> > > I would agree with Doug. We're in the days of tab-completion, and > typing 'in' will suffice to get there. I for one *hate* numbers > in paths; it takes one's hand off the letters. Also, I had to look up > i18n to find out what it was... Categories should be immediately > descriptive. > > Also, the French have to use Shift to type numbers; it's even more of > a pain for them! > > Chris > > You have struck a chord with numbers in the path, reminds me of the pre-Xorg days with /usr/X11R6, not sure what I disliked more, the capital letters or the numbers! I hereby relent, and yield to the logic of the arguments placed before me, I now agree that using internationalization for the category name is a better idea. Thanks for your persistence folks, the feedback is appreciated :) Thomas -- Thomas Abthorpe, FreeBSD Ports Committer tabtho...@freebsd.org, http://people.freebsd.org/~tabthorpe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 19, 2009 10:20:18 am Thomas Abthorpe wrote: > It was my original thought to use localization as the category nane (and > certainly something I would still hear arguments for), localization *is* > l10n. While simply using internationalization seems misleading, the use of > i18n carries a more direct conveyance. > > I posted an email to freebsd-i18n@ yesterday after posted this original > message. I asked interested parties to weigh in on the matter. This thread seems to have gone cold, so I am trying to breath a little more life into it. I have received a lot of positive feedback off line. I found this great article at the W3.org website, http://www.w3.org/International/questions/qa-i18n To paraphrase a couple of key points "Localization refers to the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market (a "locale")." ... "Internationalization is the design and development of a product, application or document content that enables easy localization for target audiences that vary in culture, region, or language." To have localization, you need internationalization, so from this, I stand by my original proposal of i18n. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkpAGE8ACgkQ5Gm/jNBp8qCXcgCfTxGr2dCRez6kIUO7E/qW6Eh2 z4sAni0skY5TK/DUnTkP4PCtmRJUr303 =MA7+ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 19, 2009 03:07:53 am Johan van Selst wrote: > Doug Barton wrote: > > > Should this new category come to being, the self identified ports in > > > misc would get relocated. All other ports would simply be extended with > > > the new virtual category name. > > > > You've probably already covered this, but are you making a distinction > > between ports that are used to _do_ localization-related tasks, and > > ports that are localized versions of existing ports? > > I think that this is an important distinction; and personally I would > expect only the previous ports to go into this category. That is, > putting ports into categories primarily based on the functionality of a > port. For example when looking for a port like firefox-i18n, I'd expect > to find it in the www/ category, rather than an i18n/ subdir. But ports > like gettext or other localization tools could be in the i18n category. That is esseintally what I hope to achieve, i18n/l10n ports in misc get moved to this new category, all others keep their original home, and extend their CATEGORIES to include the new name. Similarly gettext and other related tools could have their CATEGORIES updated as well. > > > Ciao, > Johan Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAko7n6EACgkQ5Gm/jNBp8qDiFgCfVqyzIvkZpHBA9JoE+Tit69eI EW4AnRwka4FKyNBbuSe4zNBi8T4nfH5L =CpN6 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [RFC] New category proposal, i18n
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 19, 2009 02:50:12 am Doug Barton wrote: > Thomas Abthorpe wrote: > > I would like to propose a new ports category, i18n, it would become the > > new home, physical or virtual, for ports that are i18n or l10n based. > > > > While researching the topic, I found the two terms, i18n and l10n, are > > often used interchangeably, and while either word could be used as the > > new category name, I chose i18 because it seems to keep in line with the > > efforts of freebsd-i18n team. > > While I (as an ignorant 'merican) would tend to agree with you that > the terms are close in meaning, my experience is that the people who > care about the differences _really_ care about them. Rather than have > FreeBSD appear to take a position on the debate I would suggest that > we use a term that is both neutral and more descriptive, like > "localization" or something similar. It was my original thought to use localization as the category nane (and certainly something I would still hear arguments for), localization *is* l10n. While simply using internationalization seems misleading, the use of i18n carries a more direct conveyance. I posted an email to freebsd-i18n@ yesterday after posted this original message. I asked interested parties to weigh in on the matter. > > That said I think that anything we can do to encourage localization as > a goal we should do. > > > Currently in the ports tree there are about 220 ports with i18n or l10n > > as part of their package name. Of these ports 159 are in the misc > > category, virtually all of which are related to KDE or Qt. > > > > Should this new category come to being, the self identified ports in misc > > would get relocated. All other ports would simply be extended with the > > new virtual category name. > > You've probably already covered this, but are you making a distinction > between ports that are used to _do_ localization-related tasks, and > ports that are localized versions of existing ports? It is my intention for ports that do localization related work would remain in their existing category, and if appropriate we could add the new name to CATEGORIES. Identified i18n/l10n ports outside of the misc category, would remain in their substantive cateory, and be extended to include the new category name. For instance www/dillo-i18n www/drupal5-i18n www/firefox-i18n www/firefox3-i18n www/zope-i18nlayer would all remain in in www, then we would have the CATEGORIES include i18n (or whatever) > > > hth, > > Doug Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAko7nqgACgkQ5Gm/jNBp8qBEeQCggTKW1jN6tzA9nPgG3AbJnbAz RRcAmwVm/QrTWAqmzfqPIKT3TA3n5PuM =e1Ze -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
[RFC] New category proposal, i18n
I would like to propose a new ports category, i18n, it would become the new home, physical or virtual, for ports that are i18n or l10n based. While researching the topic, I found the two terms, i18n and l10n, are often used interchangeably, and while either word could be used as the new category name, I chose i18 because it seems to keep in line with the efforts of freebsd-i18n team. Currently in the ports tree there are about 220 ports with i18n or l10n as part of their package name. Of these ports 159 are in the misc category, virtually all of which are related to KDE or Qt. Should this new category come to being, the self identified ports in misc would get relocated. All other ports would simply be extended with the new virtual category name. Taking off my KDE hat, this new category could obviously be used by anybody who is involved some sort of translation effort. As per the Porters Handbook, http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categories.html#PROPOSING-CATEGORIES, I hereby open discussion on the matter. If there is enough interest, I will pursue the matter further with portmgr@ Thank you for you time, attention and feedback. Thomas -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: dropping maintainership
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On June 16, 2009 09:48:52 am Sahil Tandon wrote: > On Jun 16, 2009, at 8:56 AM, Chess Griffin > > wrote: > > audio/streamripper > > irc/bip > > I can take these two if not already claimed. > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" Sahil I see streamripper needs and update, claim that one via PR with update, and ping me, I will try claim it and transfer bip at the same time. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAko3p7UACgkQ5Gm/jNBp8qCQEwCeOCWU9nCJY52ZlM800LyPq1Ed 1hUAnjuIjqZwm2UmvDrCXFuosYXxqubb =y8An -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On March 5, 2009 01:13:29 am Volodymyr Kostyrko wrote: > How about adding the mentioned script as periodic weekly job? Let it be > disabled by default. > > I'm monitoring a bunch of machines and I think I'll be much happier with > periodic warnings about ports which can require more then just > submitting a PR. Thanks for the suggestion, Volodymyr. It would make for an interesting project, wouldn't it :) Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkmv1eAACgkQ5Gm/jNBp8qBL7ACfcQbEqyp/2TymkVXmouUGGnvh 31AAnj97G9G7NU/cg+KEcL0GDgUKGxkG =GWwQ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On the lookout for maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At any given time, approximately 20 - 25% of all ports are unmaintained. Not all unmaintained ports need updating, but some do. That is where you folks come in. I have summarised some details at the wiki about Adopting Ports, http://wiki.freebsd.org/PortsTasks#head-f018f566bce2ff96ec13fabd536d7cc6dc6f4275. In the last Maintainer Roundup, we passed off ports to those who replied to the list with their request. This practise will not be continued. It is important for maintainers to learn the process of submitting a PR to update their port. Now check out the portscout for unmaintained ports, http://www.portscout.org/po...@freebsd.org.html, and see what you you can do up adopt and update one of these unloved, uncared for ports! The challenge has been made, it is up to you folks to rise up to it! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmrN1UACgkQ5Gm/jNBp8qAT1gCfdWaqXZ0tLvifPBbE4EnUHak8 gu0AnjbZEVNUPHGxAyyoIotZSAkZHDRY =BjQl -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On March 1, 2009 11:49:56 am Ulrich Spörlein wrote: > Not sure if these have already been taken, but sign me up for: > > audio/mp32ogg > games/freebsd-games > graphics/feh > sysutils/wmtop > x11-clocks/wmtimer > x11/wmcliphist Assigned! - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmrNnEACgkQ5Gm/jNBp8qDopgCeICYEXpdvZQYzaKG6GQMqtb28 t2UAnR3N4F+9iKXCSOjg8+ZRN4rRyS5x =jjbo -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Summary of recent Maintainer Roundup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Earlier in February, I put out a plea to find maintainers for unloved, unmaintaintained and uncared for ports. I threw down the gauntlet and people responded. To you, a tip of my hat, and a resounding thank you for stepping up! Since that time, we passed of over 100 ports to 16 willing maintainers. For fear of being procmail'd > /dev/null, I will sporadically send out similar calls for maintainers. Let us keep the momentum going folks, keep up the good work, and please watch for my next announcement! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmpgeIACgkQ5Gm/jNBp8qAU1ACfS9r8XfyC3F06UbgG7PL5phQp waMAoIDxh/6L9ZoHQ3emdmLj28CWYoj4 =2m1j -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 27, 2009 12:00:00 am Yoshihiro Ota wrote: > Let me take these, too. > > japanese/kakashi > sysutils/phantom > > Thanks, > Hiro Assigned - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmn9XIACgkQ5Gm/jNBp8qAVCgCeNMYogGl8kUYVPoKBlvPzBOA/ vdkAnjc0YaGZn1kDjoaB8WCO84GujF/K =PP4o -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 22, 2009 05:24:22 am martinko wrote: > I might try adapting the following which I use: > audio/vorbisgain > devel/rlwrap > emulators/atari800 > graphics/wmicons > sysutils/asapm Assigned :) - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmjcFEACgkQ5Gm/jNBp8qC3TgCfQYavBwGfrSufGVgltDIYazGM u5kAnRxk3I6RswVhkt41Px6B5w2XOau7 =ulOI -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 23, 2009 01:20:48 am Yoshihiro Ota wrote: > Thank you for your hard work, Thomas. Thanks Hiro :) > > Can I make 2 suggestions? > > 1. Can you ask PR senders if they are intersted in becoming maintainer if > port doesn't have a maintaner? Sender was moticvated enough to make a > patch. Agreed, this is something we should be more deliberate about doing. > > 2. Can you assign two or more maintaners to a port? This may improve > response time of PRs. As linimon@ pointed out later in this thread it has been discussed, but seems the framework is not in place. That said, a well placed comment field in the Makefile indicating a name/email of a person who has implicit submission rights could be helpful. While the automated assignment tools won't catch it, a committer might. > > Regards, > Hiro Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmir0oACgkQ5Gm/jNBp8qD60QCfRV5M9Bd0nXIA7zAnEC3ooU6H jPUAniMz/GhtVXOJqbVC8/uYXnpfobW4 =Z0mw -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 18, 2009 06:52:49 am chifeng wrote: > I sent three PRs that update these ports to latest version, So could you > assign to me? > > net/delgate net/delegate :) > mail/libpst > net-mgmt/pftabled They are yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmcIC4ACgkQ5Gm/jNBp8qA6pQCggg1fzP/XCe5hW2gDucchBX7t WkoAn0p2gZBsQXyxFRydQY+eR4ImD8vV =A/T3 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 17, 2009 10:19:34 pm Yoshihiro Ota wrote: > Let me try these, first. > > japanese/gawk > lang/mawk > lang/nawk > > Thanks, > Hiro They are yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmbovwACgkQ5Gm/jNBp8qAtWwCePwf3mS91fsPCrwhlsFTPMC0w ByIAniftWkPLFHGhxyydzibIZTTAP0oc =Jea1 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Follow up to Ports Maintainer Roundup 2009
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 14, 2009 01:46:23 pm Cezary Morga wrote: > Thomas Abthorpe wrote: > > Do us all proud, and show us what you are made of! > > So, how about me picking up > devel/p5-Config-IniFiles > devel/p5-Config-Record > devel/p5-Config-Simple > devel/p5-Config-Std > devel/p5-ConfigReader > net/wakeonlan > net/wol > net/gspoof > ? They are now yours. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmaMYcACgkQ5Gm/jNBp8qCSzACfS/IGYe7KczBa/7n2kWgKFU+E M4EAn0WV/nBx5HMAkdyWjti5EHbp1GrB =uEFT -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 14, 2009 09:29:07 am chifeng wrote: > mail/fdm > mail/p5-IMAP-Admin > mail/p5-MIME-Lite this one was already taken :( > mail/p5-MIME-Lite-HTML > mail/p5-Mail-Alias > mail/p5-Mail-Folder > mail/p5-Mail-MailStats > mail/p5-Mail-SRS > mail/p5-Mail-Spool > mail/p5-Mail-Verify > mail/popcheck > mail/rss2email > mail/sqlgrey > > Otherwise, I want to take these ports, as I am using that port. > benchmarks/iozone > benchmarks/iozone21 All others are yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmaJ7oACgkQ5Gm/jNBp8qA/zACcC8gbxcPSEoKVHxWby4EJBYn2 wS8AnRS09TyMqACnbGXIdxph08KkVLP7 =zU3C -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: xclip port update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 13, 2009 01:10:05 pm Eitan Adler wrote: > I am working on updating xclip to version 0.11 and I ran across the > following problem: > I tried with and without the attached patch. > > > Stop in /extra/ports/x11/xclip. > > Second issue how do you deal with sourceforge hosted projects? I'm > currently using /one/ of the mirrors which is not the preferred way of > doing things. A couple of things, Eitan. Remove PORTREVISION=1 When a sourceforge project is the same as the portname (which xlip is) it is as simple as MASTER_SITES= SF You will likely need to use USE_XORG= x11 xproto xmu As nivit@ said, try USE_GMAKE= yes There may be more things, but this is a good starting point for you. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmVy6kACgkQ5Gm/jNBp8qAC4QCfU8BA59yk3TEnm4yzNe6w+XPO HLoAoIG1QnJPG/rHfo7I3vPzeFlxV1/3 =J//E -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Follow up to Ports Maintainer Roundup 2009
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 13, 2009 11:59:45 am hideo wrote: > Thomas - I can take the following as well: > > devel/p5-Date-Calc > mail/crm114 Assigned :) - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmVq0cACgkQ5Gm/jNBp8qDhwQCaAoX/BNUM3VCaQV2wQLeGxN+g vhcAn2oesf/w8/mQ5U1/w07G5I1CGrl0 =qkEC -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Follow up to Ports Maintainer Roundup 2009
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We have had a flurry of activity, as you will see from the commit logs. We have had a lot of folks pick up and gauntlet, and adopt a lot of ports. A tip of my hat to the group of you! In some of these cases, we have handed over maintainership to some novice maintainers who are prepared to make a go of it. So, the next challenge, particularly to the new maintainers, go out and generate some PRs. Get those ports updated! It is listed at the wiki, but I will say it again here, check out http://www.portscout.org, scroll down to your email address see how many of your ports are out of date. Also, go to http://portsmon.freebsd.org/portsconcordanceformaintainer.py, and query your email address, see if there are any outstanding issues with your new ports. Do us all proud, and show us what you are made of! Thanks again all! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmVoT8ACgkQ5Gm/jNBp8qDF/QCggXYdyoGgD8HgtluBF9fI+Evm RAUAn2X8TgekC3Ve9ieOHKp5kWUthAyl =jdq9 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 13, 2009 12:33:12 am Sergey N. Voronkov wrote: > Most of them are dead, but still working for me quite well. ;-) > I'll try to keep it building until I can do that. They are now your, Sergey! - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmVknUACgkQ5Gm/jNBp8qAdqQCfSePRcELYlvR2xtho4m6oEkm/ nqIAmwSW8eOcWsls7lhAyPiPWSdAubFJ =V+AZ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 07:15:50 pm Eitan Adler wrote: > I'll take x11/xclip in addition to what I currently maintain. I'm > looking through the others and will submit a followup email soon. Hi Eitan They are now yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmU1OgACgkQ5Gm/jNBp8qDp5QCfVVKUxH8G2gRcfne1+gCv8Oz0 jOUAn0bSly2NmZ22VRcqnQkWi37bTRpD =LSk0 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 06:14:04 pm Daniel Roethlisberger wrote: > I'll adopt these two additional ports: > > security/md4coll > security/fragrouter > > Thanks! Hi Daniel, these ports are now yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmU1D8ACgkQ5Gm/jNBp8qBesQCfcjgqipudQCeUuI/I7wU57ECB MZ4AnRq6Za7x9Xg8+1eQ6PPkLDguiAqg =1lfk -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 05:51:26 pm Glen Barber wrote: > databases/kmysqladmin > palm/palmpower > palm/palmos-sdk > palm/prc-tools > security/portsentry These too, are yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmU0d0ACgkQ5Gm/jNBp8qC9twCghDFfZlrGh1eA5CULsOi57QVZ 11oAnj8u5hlEskWU6ibnI0SslQbaMN4b =Msf5 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 05:04:07 pm Glen Barber wrote: > I'll take the following: > lang/open-cobol > lang/tinycobol > devel/c_c++_reference Committed, they are now yours! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmU0cUACgkQ5Gm/jNBp8qAG5wCggFA0nxjvQChFKTQ95xM3O8aQ vpsAnjqnYAMfun/oEtUF1Fr7/+6Hc7Q1 =sRyP -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 04:38:21 pm hideo wrote: > I can take pacpl and it's dependencies: > > audio/pacpl > audio/kexis > audio/p5-Audio-Musepack > audio/laudio > audio/lpac > audio/optimfrog > audio/gsm The are yours! You might want to find alternate mirrors to CENKES :) Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmUz6oACgkQ5Gm/jNBp8qBBSQCdHCkLTjP7m02dQ554qzYvOiBf tdQAn17MEp89Y331tYv409X6PBCmI70T =Mb8W -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 05:04:07 pm Glen Barber wrote: > I'll take the following: > lang/open-cobol > lang/tinycobol > devel/c_c++_reference > > Should I submit a separate PR for each? Thanks Glen In this case, a PR is not necessary, we will queue it up on our todo list. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEUEARECAAYFAkmUpa0ACgkQ5Gm/jNBp8qAGVwCUDANJZ4hdGli8DIak4DxWtQsC twCfY//iUoYYP5o5W/BA0PblUMcbLOo= =r9Cr -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 04:38:21 pm hideo wrote: > I can take pacpl and it's dependencies: > > audio/pacpl > audio/kexis > audio/p5-Audio-Musepack > audio/laudio > audio/lpac > audio/optimfrog > audio/gsm Thanks Zach, we will queue it up on our todo list. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmUpW0ACgkQ5Gm/jNBp8qANYgCeMPntIhry74uPxwDos78WHLby LVQAnRBYmfg8ga+c9kns7Naf2KQAQJpq =GsaR -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 04:18:44 pm Paul Schmehl wrote: > I might also point out that it's perfectly fine to submit PRs for ports you > do not maintain. So, even if you think you can't or don't have the time to > be a maintainer, you can always submit patches for ports that are broken. You are absolutely correct, Paul. PRs can be submitted for any port, regardless of ownership. It was my intention with this drive to find proactive maintainers for ports. To take them in, and give them the time and attention they deserve. > > I'll poke around and see if there's anything additional that I can take on. Great, looking forward to hearing from you! Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmUpSEACgkQ5Gm/jNBp8qDr3QCdH7s4DS8+sx+i/dljNfiUYvjA 8OgAn3lhP6TExtoDE2uKrHtO+CnaZRcQ =dLPn -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Call for potential ports maintainers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On February 12, 2009 02:26:46 pm Paul Schmehl wrote: > How about providing a list of the ports that need maintainers? I already > have 15. I might take some more, but not until I know what they are. Thanks for the nudge, Paul! Instead of a list of ~4700 ports, here are some useful URLs - From the portsmon cluster http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=ports%40FreeBSD.org - From freshports.org Unmaintained http://www.freshports.org/search.php?stype=maintainer&method=exact&query=ports%40FreeBSD.org Broken http://www.freshports.org/ports-broken.php Deprecated http://www.freshports.org/ports-deprecated.php There are some other great stats at freshports, just do a little clicking around there. Thomas - -- Thomas Abthorpe | FreeBSD Committer tabtho...@freebsd.org | http://people.freebsd.org/~tabthorpe -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmUhXUACgkQ5Gm/jNBp8qCqHgCfUbDJmcjV2jqvCtVOiGs/gxKC uEcAn0UAE06pSlBGvempbtLvvMD1c/uy =Az2D -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
