Re: Clang as default compiler November 4th
On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote: > As of last week, 4,680 ports out of 23,857 failed to build with clang on > 9-amd64. That's almost a 20% failure rate. Until we have better support > for either building ports with clang, or have better support for the > idea of a "ports compiler," this change is premature. The ports are an > important part of the FreeBSD Operating _System_, and pulling the > trigger on the default compiler before the ports problems are addressed > robustly seems like a big fat FU. > > That said, I agree that this issue needs to be addressed. In fact, 9 > months before the release of 9.0 I said on the internal committers list > that there was no point in making a new release until we had thoroughly > addressed both the default compiler for the base, and resolving the > "ports compiler" issue. While there has been some movement on the > former, there has been nothing done on the latter for years now, even > though everyone agrees that it is an important issue. > > I'd like to request that rather than moving the default compiler > prematurely that you call for volunteers to address the problems with > the ports. Both the issues of fixing more ports to build correctly with > clang, and the issue of defining a "ports compiler" version of gcc (and > appropriate infrastructure) for those that can't. Once those issues are > resolved there would not be any further obstacles to moving the default. > Until they are, the change is premature. > > Doug Doug, as you can already use CLANG instead of GCC now, you will be able to use GCC instead of CLANG after November 4th. At the moment the ports maintainers don't give much about if their ports build with CLANG or not because they're not forced to. Those who don't run CURRENT won't notice, but those who do will have to get their butts up and fix the ports, so 10.0 can have 99% of all ports build with CLANG and even 8.x and 9.x can already profit from having the broken ports fixed now. pgpFIV5jKkyQL.pgp Description: PGP signature
Re: Clang as default compiler November 4th
On 09/11/2012 02:27 AM, Lars Engels wrote: > On Mon, Sep 10, 2012 at 10:54:04PM -0700, Doug Barton wrote: >> As of last week, 4,680 ports out of 23,857 failed to build with clang on >> 9-amd64. That's almost a 20% failure rate. Until we have better support >> for either building ports with clang, or have better support for the >> idea of a "ports compiler," this change is premature. The ports are an >> important part of the FreeBSD Operating _System_, and pulling the >> trigger on the default compiler before the ports problems are addressed >> robustly seems like a big fat FU. >> >> That said, I agree that this issue needs to be addressed. In fact, 9 >> months before the release of 9.0 I said on the internal committers list >> that there was no point in making a new release until we had thoroughly >> addressed both the default compiler for the base, and resolving the >> "ports compiler" issue. While there has been some movement on the >> former, there has been nothing done on the latter for years now, even >> though everyone agrees that it is an important issue. >> >> I'd like to request that rather than moving the default compiler >> prematurely that you call for volunteers to address the problems with >> the ports. Both the issues of fixing more ports to build correctly with >> clang, and the issue of defining a "ports compiler" version of gcc (and >> appropriate infrastructure) for those that can't. Once those issues are >> resolved there would not be any further obstacles to moving the default. >> Until they are, the change is premature. >> >> Doug > > Doug, as you can already use CLANG instead of GCC now, you will be able > to use GCC instead of CLANG after November 4th. There's lots of things I _can_ do, what we're discussing is what the defaults should be. > At the moment the ports maintainers don't give much about if their ports > build with CLANG or not Do you follow ports development? At all? There have been extensive efforts over the last several years to get more ports compiling with clang. The problem is that things like the c89 issue don't percolate down, and we don't have a concerted effort from all of the relevant parties to improve the issue. Fixing the problem of getting the right eyeballs on the things that need fixing won't be improved by switching the default before they are fixed. In fact, it's likely to make the people who are src-centric now even less likely to help because their work will be "done." > Those who don't run CURRENT won't notice, but those who do will have to > get their butts up and fix the ports, so 10.0 can have 99% of all ports > build with CLANG and even 8.x and 9.x can already profit from having the > broken ports fixed now. Yeah, and I'm going to get a pony out of this deal, right? :) You completely misunderstand the nature of the problem, therefore your proposed solution isn't going to solve it. Doug ___ 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] Announcing the end of port CVS
On Mon, 10 Sep 2012, Kevin Oberman wrote: If you want ot update all graphics ports, 'svn up /usr/ports/graphics'. For just updating a single port, 'svn up /usr/ports/graphics/ImageMagick'. But it appears that you chose to not follow the instructions. There is a reason to delete the existing ports tree and do a checkout. If you don't, every time something gets updated, it will generate a conflict as the pre-existing ports tree is not recorded in the .svn file, so svn sees the existing file as in conflict with the new one and refuses to download the new one until the conflict is resolved. (Replying to a random post.) I haven't seen this asked so far so I'll do it. Is there a cookbook procedure to create a local svn server similar to the one you posted for a single machine update? f.e.: [1] create user, group and directory [2] cd / [3] su [4] svn ... etc. I have read the FreeBSD svn page and red-beans.com and neither has one or if they do I haven't been able to find it. Thanks, Frank -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.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" ___ 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: x11-toolkits/swt
2012/9/11 Doug Barton : > Now that we have a new version of libxul in the ports tree, any plans of > upgrading swt to take advantage of it? I'd love to get the > vulnerabilities in the old version off of my daily periodic. Meanwhile, I've had success with x11-toolkits/swt-devel for mail/davmail and java/eclipse (btw, for me eclipse compiles only if swt-devel is installed, not swt). -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: Clang as default compiler November 4th
--On September 11, 2012 2:44:03 AM -0700 Doug Barton wrote: Doug, as you can already use CLANG instead of GCC now, you will be able to use GCC instead of CLANG after November 4th. There's lots of things I _can_ do, what we're discussing is what the defaults should be. At the moment the ports maintainers don't give much about if their ports build with CLANG or not Do you follow ports development? At all? There have been extensive efforts over the last several years to get more ports compiling with clang. The problem is that things like the c89 issue don't percolate down, and we don't have a concerted effort from all of the relevant parties to improve the issue. Fixing the problem of getting the right eyeballs on the things that need fixing won't be improved by switching the default before they are fixed. In fact, it's likely to make the people who are src-centric now even less likely to help because their work will be "done." Those who don't run CURRENT won't notice, but those who do will have to get their butts up and fix the ports, so 10.0 can have 99% of all ports build with CLANG and even 8.x and 9.x can already profit from having the broken ports fixed now. Yeah, and I'm going to get a pony out of this deal, right? :) You completely misunderstand the nature of the problem, therefore your proposed solution isn't going to solve it. Perhaps a port maintainer's input would help? I'd never even heard of clang until recently. I'm not a programmer. If I can't get my ports to compile with clang without a knowledge of programming, I'll abandon them. I'm too old and too tired to try learning a brand new system. I doubt I'm alone. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ 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"
some ports do not build with libxul-10.0.7
Hello, The www/libxul was updated to 10.0. It is mentioned in UPDATING with some instructions for those wanting to stay with 1.9.2. I thought I could go with the new version and updated www/libxul (using portmaster). It went OK. Now I can't build some other ports, for example deskutils/chmsee: /usr/ports/deskutils/chmsee> make chmsee is using libxul19 for gecko support, but you can change that by defining WITH_GECKO to the following values: libxul19 ===> License GPLv2 accepted by the user ===> Extracting for chmsee-1.3.1.1_3 => SHA256 Checksum OK for chmsee-1.3.1.1.tar.gz. ===> Patching for chmsee-1.3.1.1_3 ===> chmsee-1.3.1.1_3 depends on file: /usr/local/lib/libxul/libxul.so - found ... snipped ... -- checking for one of the modules 'mozilla-gtkmozembed-embedding>=1.9;xulrunner-gtkmozembed>=1.9' CMake Error at /usr/local/share/cmake/Modules/FindPkgConfig.cmake:363 (message): None of the required 'mozilla-gtkmozembed-embedding>=1.9;xulrunner-gtkmozembed>=1.9' found Call Stack (most recent call first): CMakeLists.txt:11 (pkg_search_module) -- Configuring incomplete, errors occurred! *** [do-configure] Error code 1 Stop in /usr/ports/deskutils/chmsee. Similar failure happens in www/gecko-mediaplayer. Any suggestions? TIA Oli ___ 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: x11-toolkits/swt
Hello guys; - Original Message -  ... > > 2012/9/11 Doug Barton : >> Now that we have a new version of libxul in the ports tree, any plans of >> upgrading swt to take advantage of it? I'd love to get the >> vulnerabilities in the old version off of my daily periodic. > > Meanwhile, I've had success with x11-toolkits/swt-devel for > mail/davmail and java/eclipse (btw, for me eclipse compiles only if > swt-devel is installed, not swt). > I think we can safely replace x11-toolkits/swt with x11-toolkits/swt-devel. I would also prefer to drop myself from maintainance of the swt port: I only grabbed it to make sure the updates would go to the -devel port first. Pedro. ___ 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: Plans for making MAKE_JOBS_SAFE the default?
2012/9/4 Bryan Drewery : >> My proposal: >> - start an exp-run with FORCE_MAKE_JOBS set >> - mark all new failures with MAKE_JOBS_UNSAFE >> - flip the default right after the 9.1 release. +1 too except for devel/libftdi which just failed on me right now, was ok after setting MAKE_JOBS_UNSAFE. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: ports/169643: New port: databases/py-mysql2pgsql [redports]
Synopsis: New port: databases/py-mysql2pgsql [redports] Responsible-Changed-From-To: rm->freebsd-ports Responsible-Changed-By: rm Responsible-Changed-When: Tue Sep 11 18:47:38 UTC 2012 Responsible-Changed-Why: Submitter's feedback timeout. Return this to the pool. I'd consult upstream if this extra-patch is needed. http://www.freebsd.org/cgi/query-pr.cgi?pr=169643 ___ 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: ports/169643: New port: databases/py-mysql2pgsql [redports]
Synopsis: New port: databases/py-mysql2pgsql [redports] State-Changed-From-To: feedback->open State-Changed-By: rm State-Changed-When: Tue Sep 11 18:48:53 UTC 2012 State-Changed-Why: Should be 'open', not 'feedback'. http://www.freebsd.org/cgi/query-pr.cgi?pr=169643 ___ 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: ports/169643: New port: databases/py-mysql2pgsql [redports]
Synopsis: New port: databases/py-mysql2pgsql [redports] Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs Responsible-Changed-By: rm Responsible-Changed-When: Tue Sep 11 18:51:49 UTC 2012 Responsible-Changed-Why: Should be 'freebsd-ports-bugs', not 'freebsd-ports'. http://www.freebsd.org/cgi/query-pr.cgi?pr=169643 ___ 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] Announcing the end of port CVS
On 11 September 2012 14:06, Frank Seltzer wrote: > > > On Mon, 10 Sep 2012, Kevin Oberman wrote: > >> If you want ot update all graphics ports, 'svn up >> /usr/ports/graphics'. For just updating a single port, 'svn up >> /usr/ports/graphics/ImageMagick'. >> >> But it appears that you chose to not follow the instructions. There is >> a reason to delete the existing ports tree and do a checkout. If you >> don't, every time something gets updated, it will generate a conflict >> as the pre-existing ports tree is not recorded in the .svn file, so >> svn sees the existing file as in conflict with the new one and refuses >> to download the new one until the conflict is resolved. > > > (Replying to a random post.) > > I haven't seen this asked so far so I'll do it. Is there a cookbook > procedure to create a local svn server similar to the one you posted for a > single machine update? > > f.e.: > > [1] create user, group and directory > [2] cd / > [3] su > [4] svn ... > etc. > > I have read the FreeBSD svn page and red-beans.com and neither has one or if > they do I haven't been able to find it. > > Thanks, > Frank > If you mean svnsync, that should do it for you... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html#AEN1299 You'll want to switch mirrors however. Chris ___ 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] Announcing the end of port CVS
On 9/11/2012 8:06 AM, Frank Seltzer wrote: > I haven't seen this asked so far so I'll do it. Is there a cookbook > procedure to create a local svn server similar to the one you posted > for a single machine update? > It takes less time to just follow the instructions footnoted in the original post than to read this entire thread. Since the repository UUID doesn't change with the svnsync method "svn relocate" can change an existing svn tree (i.e., /usr/src) to use the new mirror, and change to another mirror or the baseline repository later. ___ 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] Announcing the end of port CVS
On Tue, 11 Sep 2012, Chris Rees wrote: I haven't seen this asked so far so I'll do it. Is there a cookbook procedure to create a local svn server similar to the one you posted for a single machine update? f.e.: [1] create user, group and directory [2] cd / [3] su [4] svn ... etc. I have read the FreeBSD svn page and red-beans.com and neither has one or if they do I haven't been able to find it. Thanks, Frank If you mean svnsync, that should do it for you... http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/subversion-primer.html#AEN1299 You'll want to switch mirrors however. Chris I should have been more specific, my bad. I meant something like: install devel/subversion copy /svnserve.conf.sample to /usr/local/etc/svnserve.conf and edit then the rest of my list. Thanks, Frank ___ 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"
MAINTAINER lines and Real Names
Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees How would people feel about supporting that in our ports tree? I have prepared a patch that keeps the old behaviour for "make maintainer", and while I did it I couldn't help but notice that the code for make readmes actually supports such a style. http://www.bayofrum.net/~crees/patches/bsd-port-mk-maintainer-not-just-email.diff As well as being nice to see, it would also mean that addport could use the data in the MAINTAINER line to get real names back into Submitted by: commit logs (currently it only has maintainer email). As a nice extra, it would also on the surface support multiple maintainers and make maintainer would still only return the first match. Chris [1] http://www.openbsd.org/cgi-bin/cvsweb/ports/shells/bash/Makefile?rev=1.73 ___ 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: MAINTAINER lines and Real Names
On 9/11/2012 3:59 PM, Chris Rees wrote: > Hi all, > > Ever since I peeked at OpenBSD's ports [1] to see how they handle > headers, I've noticed something else nice that they do. > > Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we > have; > > MAINTAINER=cr...@freebsd.org > > they have the much more pleasant and personal style; > > MAINTAINER=Chris Rees I like this! > > How would people feel about supporting that in our ports tree? I have > prepared a patch that keeps the old behaviour for "make maintainer", > and while I did it I couldn't help but notice that the code for make > readmes actually supports such a style. > > http://www.bayofrum.net/~crees/patches/bsd-port-mk-maintainer-not-just-email.diff > > As well as being nice to see, it would also mean that addport could > use the data in the MAINTAINER line to get real names back into > Submitted by: commit logs (currently it only has maintainer email). > > As a nice extra, it would also on the surface support multiple > maintainers and make maintainer would still only return the first > match. This would definitely be a huge plus. > > Chris > > [1] http://www.openbsd.org/cgi-bin/cvsweb/ports/shells/bash/Makefile?rev=1.73 > ___ > 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" > -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ 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: MAINTAINER lines and Real Names
On 09/11/2012 03:59 PM, Chris Rees wrote: Hi all, Ever since I peeked at OpenBSD's ports [1] to see how they handle headers, I've noticed something else nice that they do. Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we have; MAINTAINER=cr...@freebsd.org they have the much more pleasant and personal style; MAINTAINER=Chris Rees I think it is a good idea. (But I thought I suggested the same idea a few days ago!) ___ 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: MAINTAINER lines and Real Names
On 11 September 2012 22:14, Stephen Montgomery-Smith wrote: > On 09/11/2012 03:59 PM, Chris Rees wrote: >> >> Hi all, >> >> Ever since I peeked at OpenBSD's ports [1] to see how they handle >> headers, I've noticed something else nice that they do. >> >> Instead of the plain, boring who-the-hell-is-this MAINTAINER line that we >> have; >> >> MAINTAINER=cr...@freebsd.org >> >> they have the much more pleasant and personal style; >> >> MAINTAINER=Chris Rees >> > > I think it is a good idea. (But I thought I suggested the same idea a few > days ago!) > Haha, so you did, and I remember reading it too. Sorry! Now there's a patch that could make it reality :P Chris ___ 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"
Csup -- svn -- portsnap -- ctm -- ???
I've always relied on local log files, script-generated files, .txt files with hints on rebuilding, .htm with usage, etc in the ports tree directories (/usr/ports/devel/subversion/Plist_Manually /usr/ports/devel/subversion/Time_toCompile /usr/ports/devel/subversion/svn_ports.msg ) etc etc. With more than one machine low on disk space vs what a fully modern PC might be, are they any hints on how to proceed when the usual csup/cvsup is deprecated? . Portsnap says it will lose local changes, and refuses to update a ports tree I restored over a fresh one (with files as the above). (It wants it created anew again...) . SVN, until I learn how, may not cleanly merge the former ports tree (with the extra files) into the new tree and let the extra files stay there (as portsnap's man page suggest it also might.) I know I could craft a thumbdrive, ftp server, etc etc solution but as this is a wholesale change of how I've always updated ports I am looking for someone else's suggestions (who use portsnap and/or ctm and/or svn, and also have extra files in the ports tree) about which methodology I might try to setup on one machine, and if it works, plan the rest before csup/cvsup deprecates (unless they remain in non-official svn>csup servers somewhere, so to speak...) Thanks J. Bouquet ___ 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: MAINTAINER lines and Real Names
On Tue, Sep 11, 2012 at 10:59 PM, Chris Rees wrote: > As a nice extra, it would also on the surface support multiple > maintainers and make maintainer would still only return the first > match. Multiple maintainers? It's the best way to make no one responsible for a port: "Should I handle the update? Oh, no matter, $someone will do it". ;) -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ 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: MAINTAINER lines and Real Names
Like with Apache, x 11, or perl? Trying to get something there committed it's like pulling tiger teeth with a pair of pliers. return I agree multiple maintainers is a bad idea. If someone is technical enough to want to maintain that, they can always use an alias it goes to a group. Oh, were talking to Apache x 11 or Perl again -- Michael Scheidell Will Hack For Food On Sep 11, 2012 5:46 PM, "Alberto Villa" wrote: > On Tue, Sep 11, 2012 at 10:59 PM, Chris Rees wrote: > > As a nice extra, it would also on the surface support multiple > > maintainers and make maintainer would still only return the first > > match. > > Multiple maintainers? It's the best way to make no one responsible for > a port: "Should I handle the update? Oh, no matter, $someone will do > it". ;) > -- > Alberto Villa, FreeBSD committer > http://people.FreeBSD.org/~avilla > ___ > 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" > ___ 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: MAINTAINER lines and Real Names
On Wed, Sep 12, 2012 at 12:50 AM, Michael Scheidell wrote: > Like with Apache, x 11, or perl? > Trying to get something there committed it's like pulling tiger teeth with a > pair of pliers. return I agree multiple maintainers is a bad idea. > If someone is technical enough to want to maintain that, they can always use > an alias it goes to a group. > Oh, were talking to Apache x 11 or Perl again Teams are a different matter, they have an organisation so they can work (exceptions to this are caused by some teams being formed by too few people). Multiple individual maintainers will never be as organised as a team can be. -- Alberto Villa, FreeBSD committer http://people.FreeBSD.org/~avilla ___ 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: MAINTAINER lines and Real Names
On 2012-09-12 00:50, Michael Scheidell wrote: > Like with Apache, x 11, or perl? > Trying to get something there committed it's like pulling tiger teeth with > a pair of pliers. return I agree multiple maintainers is a bad idea. > If someone is technical enough to want to maintain that, they can always > use an alias it goes to a group. > Oh, were talking to Apache x 11 or Perl again > I see no reason for having multiple MAINTAINERS. Commit with implicit and if you like give a statement http://wiki.freebsd.org/MaintainerNotes about co-maintaining. I already wiped my eyes on this commit http://svnweb.freebsd.org/ports?view=revision&revision=304107 Or as Alberto already explained the reasons for a team form one. @Michael Trolling or experience? $> query-pr -c ports -r apache -y scheidel -q query-pr: no PRs matched $> query-pr -c ports -r perl -y scheidel -q oh, found two PR's for 4.11 and 5.5 $> query-pr -c ports -r x11 -y scheidel -q query-pr: no PRs matched -- Regards, olli ___ 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: MAINTAINER lines and Real Names
Two lls. Direct experience with x 11 But you can see this list for many complaints about trying to get port committed owned by teams. Ps I don't troll. -- Michael Scheidell Will Hack For Food ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: MAINTAINER lines and Real Names
On 9/11/2012 6:32 PM, Olli Hauer wrote: > On 2012-09-12 00:50, Michael Scheidell wrote: >> Like with Apache, x 11, or perl? >> Trying to get something there committed it's like pulling tiger teeth with >> a pair of pliers. return I agree multiple maintainers is a bad idea. >> If someone is technical enough to want to maintain that, they can always >> use an alias it goes to a group. >> Oh, were talking to Apache x 11 or Perl again >> I see the proposal less about *FreeBSD Ports Teams* and more about *Non-FreeBSD* groups. We can only blame ourselves for having non-responsive teams, or having *mailing lists* be maintainers. I see the benefit here more about allowing us to commit PR from any of the listed addresses, as well as allow end-users to have more *people* to contact. > > > I see no reason for having multiple MAINTAINERS. > Commit with implicit and if you like give a statement > http://wiki.freebsd.org/MaintainerNotes about co-maintaining. > > I already wiped my eyes on this commit > http://svnweb.freebsd.org/ports?view=revision&revision=304107 This is less about implicit approval, and more about having more support contact for end-users. There's nothing stopping anyone from doing this in other pors, why not make it standard for 'make maintainer' to list these people. There's no harm. > > Or as Alberto already explained the reasons for a team form one. > > @Michael > Trolling or experience? > > $> query-pr -c ports -r apache -y scheidel -q > query-pr: no PRs matched > > $> query-pr -c ports -r perl -y scheidel -q > oh, found two PR's for 4.11 and 5.5 > > $> query-pr -c ports -r x11 -y scheidel -q > query-pr: no PRs matched > > > -- > Regards, > olli > ___ > 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" > -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ 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"
