Re: RFC: some patches to the Porter's Handbook

On Wed, Jun 01, 2011 at 09:10:06AM +0200, Carsten Jensen wrote: While doing the revision, would it be too much trouble to add a section for web apps ? Sorry, I don't know enough about them to add that section ... mcl ___ freebsd-ports@freebsd.org

Re: [ANNOUNCE]: clang compiling ports

On Mon, Jun 20, 2011 at 05:37:53PM +0200, Roman Divacky wrote: Flz@ just ran an exp-build with CC=clang and CXX=clang++. The results can be seen here: http://pointyhat.freebsd.org/errorlogs/amd64-9-exp-latest/ A permanent URL to this run is:

Re: GHC Port on 9-CURRENT

On Sun, Jun 26, 2011 at 03:54:28AM +, b. f. wrote: Please don't hardcode the compilers +1. One of the Next Big Tasks is to be able to use a compiler other than the system default, for ports. Please don't make this work more painful than it will already be :-) mcl

Re: [ANNOUNCE]: clang compiling ports

On Mon, Jun 20, 2011 at 06:21:26PM -0500, Mark Linimon wrote: A permanent URL to this run is: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110616185105/ That will stick around even if we use amd64-9-exp for something else. I have updated the errorlog-classifier

Re: [ANNOUNCE]: clang compiling ports

On Thu, Jun 30, 2011 at 08:19:05AM +, b. f. wrote: Is there a new link for the new results? Or did you use the link above? same link. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: Opinions sought on location of bsd.octave.mk

On Sun, Jul 03, 2011 at 03:39:06PM -0400, Sahil Tandon wrote: As you note above, Mk scripts exist in various locations, so there appears to be no consensus. However, I personally agree with the sentiment in the (somewhat dated) Wiki:

Re: cvs commit: ports/accessibility/kdeaccessibility Makefile ports/arabic/kde3-i18n Makefile ports/arabic/koffice-i18n Makefile ports/audio/arts Makefile ports/audio/juk Makefile ports/audio/mpeglib_

On Mon, Jul 11, 2011 at 08:51:02AM +1000, Peter Jeremy wrote: It would be useful if there was a mechanism to warn users that the port they are about to install (or have installed) is no longer recommended. IMHO using DEPRECATED without EXPIRATION_DATE is just fine for this. mcl

Re: RFC: change to bsd.perl.mk

If bsd.perl.mk is going to be included unconditionally, what's the point of having it in a separate file? - perl team can make changes (e.g. minor version update of perl) without -exp run and portmgr approval. (I would still prefer to do -exp runs for major version updates, of course).

Re: RFC: change to bsd.perl.mk

On Sat, Jul 16, 2011 at 10:51:04PM +0100, Chris Rees wrote: If it's unconditionally included, how does that exempt it from exp-runs? Surely it's equally risky to commit to it as bsd.port.mk, or have I missed something? In a perfect world we'd have -exp runs for everything, I suppose. OTOH

Re: french/aster ignores PYTHON_VERSION= 2.6 ?

On Tue, Jul 26, 2011 at 11:46:17PM +0400, Ruslan Mahmatkhanov wrote: Add Mk/bsd.python.mk to description field a good idea, but ... so it will be assigned to portmgr@. portmgr@ doesn't own all the bsd.*.mk files; bsd.python.mk is owned by python@. We're happy to put an -exp run in the queue

Re: Maintainership request for news/multisuck

Done. In general it's more effective to send-pr rather than post to the mailing list, which is such high-traffic. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: sysutils/diskcheckd needs fixing and a maintainer

On Wed, Aug 17, 2011 at 04:36:23PM +0200, Julian H. Stacey wrote: Better to leave the port marked as having some run errors in some circumstances, that we dont have manpower for, but leave port in tree. Then we have the situation of a user spends the time to install it only to figure out it's

Re: sysutils/diskcheckd needs fixing and a maintainer

On Wed, Aug 17, 2011 at 11:15:54AM -0500, Mark Linimon wrote: Jeremy Chadwick koi...@freebsd.org no longer involved with the project (since 2008). Actually this statement is false. He's involved with project, but not as a committer since 2008. My apologies. mcl

Re: Big patches

Sorry, I did not see your message and emailed you separately. GNATS has a spamcatcher for 500k messages (mostly this catches viruses). Normally I handle such PRs manually before the cleanup process runs, but I forgot to do it this time. (I only took a glance.) Does the plist change

Re: sysutils/diskcheckd needs fixing and a maintainer

On Fri, Aug 19, 2011 at 09:47:33PM -0700, per...@pluto.rain.com wrote: If it's OK to close a PR without fixing it, because no one seems interested, maybe we should just close 143566 and be done with it No, we're really not trying to do that. I keep trying to communicate to PR submitters that

Re: sysutils/diskcheckd needs fixing and a maintainer

On Thu, Aug 18, 2011 at 02:57:17AM +0200, Julian H. Stacey wrote: I'd question _why_ valuable people like you Chris would allow your time to be distracted merely to try to get repair run time capability of a port. I haven't spent any time on this port. I'm just trying to reply to traffic on

Re: Re-organizing the directory hierarchy?

I'm going to speak for myself and not portmgr here. My take has always been that looking through the Ports Collection should be done by some high-level search tool (e.g. website). Just looking through the raw portnames, even if they have descriptions, is mind- numbing. I don't believe that we

Re: How to escalate? ports/159276 - cmake

Well, in FreeBSD, there's really not an escalate, since we're not a hierarchy. The best thing you can do is what you've already done: contact the maintainer and, if you don't get a response, either file a PR with the suggested patch (which can later be committed via maintainer-timeout), or post

Re: How to escalate? ports/159276 - cmake

On Sat, Aug 27, 2011 at 03:35:29PM -0400, Jerry wrote: FreeBSD prefers to tell others about how great it is and conveniently hides its deficiencies. There's been plenty of honest discussion on several public mailing lists in the past 2 weeks that made some good points about what we're lacking.

Re: Ports system quality and trolling

On Sun, Aug 28, 2011 at 08:24:52PM -0400, Jerry wrote: You have also asked for and I assume received monetary compensation for your services. In Doug's case: a small percentage of his contributions over the years (e.g. for improvements to portmaster, which he had already written). I'm sure

Re: Why do we not mark vulnerable ports DEPRECATED?

On Mon, Aug 29, 2011 at 10:48:31PM -0700, Doug Barton wrote: Can someone explain why this would be a bad idea? Very early in my committer career, I marked a port BROKEN that kde depended on. I was quickly chastisted by people trying to install kde :-) So, the right answer may be it depends.

Re: Time to remove the GNUTLS option in the print/cups-client port

Could we please change the Subject line to match the content now? mcl ___ 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: cvs commit: ports/mail/procmail Makefile

On Tue, Aug 30, 2011 at 05:57:10PM +0200, Matthias Andree wrote: How about if we added a new tag OBSOLESCENT or so that permits building the software only if it's already installed but refuses new installations? Right now if you set DEPRECATED you'll get a warning. Shouldn't that be

Re: cvs commit: ports/mail/procmail Makefile

On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote: It only warns, it does not prevent fresh installs on systems that don't have the same port/package already installed. code, not policy ... ? mcl ___ freebsd-ports@freebsd.org mailing

Re: Ports system quality

On Mon, Aug 29, 2011 at 07:34:56AM +0200, Michal Varga wrote: - While nobody probably cares much about that guy and his missing browser images, what would you tell to the GIMP guy? That he should have waited longer before upgrading the (for him, 30 levels deep) Foo dependency? With furious

Re: suggestion for pkgdb from ports-mgmt/portupgrade: add more explanation

On Fri, Sep 02, 2011 at 11:39:14AM +0200, Michel Talon wrote: My point is that there shouldn't be any edge cases In a perfect world: yes. I certainly don't have any precise idea of the things which should be changed so that edge cases disappear Well, then, we're right back where we started.

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

On Sun, Sep 04, 2011 at 05:09:05AM +0200, Gerald Pfeifer wrote: Can you advise which value of __FreeBSD_version to use? The official list at http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html does not have a reference from what I can see. There is no

Re: sysutils/cfs

On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote: It is not responsible to threaten to remove ports without warning between releases for non urgent reasons. portmgr has no such policy. Ports get deleted all the time due to various issues. I prefer to see a 1- or 2-month

Re: Maintainership of py-zopetesting and py-zopeevent

On Mon, Sep 05, 2011 at 05:38:06PM -0700, Doug Barton wrote: My understanding is that we don't do port names with . in them. Can someone who knows more than I confirm one way or the other? The porter's handbook is ambiguous: The first letter of the name part should be lowercase. (The rest of

Re: Why Are You NOT Using FreeBSD?

On Mon, Jun 04, 2012 at 07:53:52AM -0400, Michael Scheidell wrote: On 6/4/12 7:36 AM, Adam Strohl wrote: Doesn't tinderbox do this every night? And, as a committer, here is the point. We get reports of 'this doesn't build'. (no fixed attached, no logs, no indication of what was installed

RFC: ports failing in jails

I'd like to request the assistance of our committers and maintainers in fixing a new failure mode of ports which are built in jails. We have recently made the port-building code more restrictive about when builds may access the net. Access to the net is now denied except in the fetch phase.

RFC: ports failing on current

Recently I was able to do a test run of ports on stock amd64-10 (gcc still as default compiler). The results suggest that we have a lot of work to do. The failures that I have documented are disjoint from the updates to php, png, libgif, and the options framework, due to the simple fact that

Re: libpng.so.6 missing

On Tue, Jun 12, 2012 at 07:19:09AM -0700, Waitman Gobble wrote: One thing - on the pkgbeta link the packages are a month old... There's been a regression with how pkgng handles lang/python* and until we fix that we can't upload new packages. mcl ___

Re: FreeBSD ports which are currently scheduled for deletion

On Thu, Jun 21, 2012 at 01:24:55PM +0200, Stefan Esser wrote: Am 21.06.2012 10:29, schrieb lini...@freebsd.org: portname: audio/gstreamer-plugins-flite description:Gstreamer flite run-time speech synthesis engine plugin maintainer:

Re: Port system problems

The intention is to move from the following: - 90% of our userbase use ports, 10% use packages to - 90% of our userbase use packages, 10% use ports so that we can save people a dreadful amount of time and hassle. That's really all that is happening here. mcl

Re: [HEADS UP] Ports tree migration to Subversion

On Sun, Jul 08, 2012 at 11:05:29PM -0400, Thomas Mueller wrote: pkgsrc is NetBSD's version of FreeBSD ports framework but also ported to other, mostly (quasi-)Unix OSes including even FreeBSD. To correct a misapprehension: although many years ago pkgsrc and FreeBSD ports shared common ancestry,

Re: maintainer timeout for FreeBSD commiters

On Tue, Jul 17, 2012 at 07:54:59AM -0400, Michael Scheidell wrote: We *are* making progress in cutting through the backlog though. ports have about 900 open PR. Why it does not have more port commiters? Its difficult to recruit new person? The answer to that is very complex. And, for each PR,

Re: maintainer timeout for FreeBSD commiters

On Wed, Jul 18, 2012 at 12:09:50AM +0200, John Marino wrote: Would it be so bad if all my submitted patches (as a recognized quality contributor with history) just got committed as a passthrough? This has been explored on the mailing lists before, however, we don't technically have a way to do

Re: Hydrogen drum machine

On Fri, Jul 20, 2012 at 04:43:56PM +0200, Bernt Hansson wrote: Why is audio/hydrogen marked as broken? On the package building cluster it failed to install correctly: http://www.freebsd.org/cgi/cvsweb.cgi/ports/audio/hydrogen/Makefile See rev 1.27. mcl

announcing the availability of packages for the Arm architecture

With the help of Alexander Motin, I have now started limited package builds on the Arm architecture. Right now builds are only being done for a few hand-selected ports, and only on arm-9 with pkgng. No builds with the old pkg_* tools are intended at this time. For those of you with Arm systems,

Re: svn commit: r303789 - head/Mk

On Fri, Sep 07, 2012 at 01:25:24AM +0200, Juergen Lock wrote: This seems to cause add-plist-buildinfo targets not found outside tb, I guess you meant this? Yes, you are right. bdrewery appears to have already fixed it. mcl ___

Re: Clang as default compiler November 4th

On Tue, Sep 11, 2012 at 11:27:50AM +0200, Lars Engels wrote: 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. I think this is a mis-representation. Adding the requirement your ports must work on clang is adding an

Re: Clang as default compiler November 4th

On Wed, Sep 12, 2012 at 03:03:43PM +0200, Lars Engels wrote: two of the ports I maintain don't build with CLANG, yet. I just checked that on the wiki page [1]. To repeat myself, the ports I've listed on that page are the big problems. People need to look at the errorlogs URLs up at the top to

Re: Clang as default compiler November 4th

On Thu, Sep 13, 2012 at 08:21:31AM +0200, Pietro Cerutti wrote: On 2012-Sep-11, 23:29, Doug Barton wrote: What we need to do is what I and others have been asking to do for years. We need to designate a modern version of gcc (no less than 4.6) as the official default ports compiler, and

[HEADSUP] FYI: patch to ports that do not build with clang has been committed

The commit mail hasn't gone through yet, so I guess I need to post this first and reference the commit mail later. Sometime in the near future, the default CC on -current will be switched to clang. The patch I have committed is a workaround -- an interim measure -- to get ready for this

Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed

On Wed, Oct 10, 2012 at 05:11:07PM +0200, Roman Divacky wrote: Can we arrange exp builds with FORCE_BASE_CC_FOR_TESTING=clang that will report all ports with USE_GCC=* but build with clang? Sure. That was kind of the intention. mcl ___

Re: Fwd: ports/172559: ports/sysutils/apcupsd failed to build in i386 machine with USB driver enabled

We have been working on the infrastructure machines. Please try pulling up the page again and see if it works now. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: Index not being built again

On Wed, Oct 24, 2012 at 10:21:45AM -0700, Kevin Oberman wrote: Looks like the index build is broken again The machine that builds the port index was physically moved on Sunday. Expect a few more interruptions before everything is sorted out. mcl ___

Re: Is PR database updated?

On Fri, Nov 16, 2012 at 08:13:47AM +0100, Fernando Apesteguía wrote: Is there some problem with the PR database? The web part of the database is not updating. We are working on it. mcl ___ freebsd-ports@freebsd.org mailing list

Re: multimedia/x264 workaround is broken

On Wed, Dec 26, 2012 at 05:41:19PM +0100, Dimitry Andric wrote: Unfortunately the original build logs which pointed out the error have been lost, apparently due to the security incident. s/have been lost, apparently/are offline/ mcl ___

Re: multimedia/x264 workaround is broken

On Mon, Dec 31, 2012 at 04:12:54PM +, Matthew Rezny wrote: Is it expected the build logs will be online again at some point? I would like to see them back online, but it's not under my control. mcl ___ freebsd-ports@freebsd.org mailing list

Re: Status of ports update submitted 2 months ago

On Fri, Jan 04, 2013 at 11:11:54PM +0100, Michael Grünewald wrote: The PRs used to be listed by portsmon but I recently noticed they disappeared. [1] portsmon is running off of a stale mirror of the database. I keep forgetting to go figure out the new mirror process. I apologize. mcl

Re: what's up with portsmon?

On Tue, Aug 26, 2014 at 04:34:01PM -0700, Don Lewis wrote: What's going on with portsmon.freebsd.org these days? A number of my ports have been updated quite a while ago, but there isn't any updated build status on portsmon. portsmon suffered some bitrot when a vuxml URL grew a | in it.

Re: Building subversion-1.8.10 under poudriere

On Wed, Aug 27, 2014 at 05:30:22PM -0500, Lawrence K. Chen, P.Eng. wrote: Wonder if there's still time to now see what ports I have installed that haven't been staged yet? This doesn't quite answer your question, but there's a portsmon page listing all nonstaged ports:

Re: Giving Up Maintainership

On Mon, Dec 15, 2014 at 08:09:48AM -0600, Rusty Nejdl wrote: Sorry guys, but I will have to give up maintainership on my 10 ports as I have completely run out of time and am not keeping up with my ports and keeping them to standards. I'll jump back in when I can and thank you all in advance.

Re: https://svnweb.freebsd.org/ Attic URLs, eg for ports/mail/demime ?

On Sat, Dec 27, 2014 at 08:20:45AM -0700, Warren Block wrote: I think I could make a good case for moving that ports FAQ into the Porter's Handbook, even if it is for committers. Sounds good. mcl ___ freebsd-ports@freebsd.org mailing list

Re: How does the Additional FreeBSD Contributors page work?

On Thu, Jan 01, 2015 at 06:05:38PM -0800, Chris H wrote: Would anyone be willing to clarify? Or am I simply blacklisted? ;) The list is not complete. No doubt you've merely been overlooked, sorry. mcl ___ freebsd-ports@freebsd.org mailing list

Re: BIND REPLACE_BASE option

On Sun, Jan 11, 2015 at 03:54:39PM -0800, Roger Marquis wrote: time for it to go, by whose definition? Good code doesn't have a fixed lifespan and the claimed rationale doesn't constitute a good business case. It was believed to be a bad design pattern to let ports modify anything in base.

Re: BIND REPLACE_BASE option

On Sun, Jan 11, 2015 at 10:38:50PM -0800, Craig Rodrigues wrote: Wrong. I've worked at 3 companies over the years that make direct use of the ports tree when creating an embedded product based on FreeBSD. OK, then this is the first I've heard of it. My mistake. mcl

Re: BIND REPLACE_BASE option

On Mon, Jan 12, 2015 at 01:29:32PM +0100, Michelle Sullivan wrote: Just a thought: FreeNAS FreeNAS uses ports ... in their own way. Yes, they do contribute back changes as well. The point that I was trying to make, even though I used bad data, was that Ports aren't being driven by external

Re: Time to be real

Thank you for your troll. For your convenience, we will do our best not to reply to you any further, to waste either your time, or valuable electrons. mcl ___ freebsd-ports@freebsd.org mailing list

Re: Synchronising ports with package cluster

On Wed, Apr 15, 2015 at 08:55:23AM -0700, Kevin Oberman wrote: My thanks to whoever made this possible. New hardware of this sort is a bit expensive and the time of those who can integrate it all is invaluable. I'm not the one working on this so I'm somewhat butting in, however: You guys

Re: New pkg audit / vuln.xml failures (php55, unzoo)

On Wed, Jun 10, 2015 at 11:45:29PM -0600, Janky Jay, III wrote: Hrm... Numerous inquiries regarding this and no response is somewhat disappointing. This is not an excuse, but a number of us are at BSDCan and distracted. There have been discussions about how to solve the larger ports security

Re: Hi, I'd like to update the coreos-etcd port!

On Tue, Nov 10, 2015 at 09:36:48AM -0500, John Barker wrote: > I went through the earlier steps about finding any outstanding issues, I > can't see any pending PRs here: > http://portsmon.freebsd.org/portoverview.py?category=devel=etcd= > am I looking for it wrong? No, that should be correct.

Re: Can we bring back sysutils/cronolog?

On Sun, Nov 29, 2015 at 02:24:53PM -0800, Chris H wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199851 > It has a workable patch. But no one appears to want to commit it. "No one has gotten to it yet" is different from "no one appears to want to commit it". The ports PR count stands

Re: Removing documentation

On Sun, Feb 07, 2016 at 03:21:49PM +0100, John Marino wrote: > Anybody proposing to be maintainer, in my opinion, should first be > required to take over every open PR in bugzilla thus ensuring that no one would ever take it. IMVVHO. mcl ___

Re: suggested patch for bsd.ports.mk

On Sat, May 14, 2016 at 11:25:08AM +0800, Julian Elischer wrote: > so who or what decides if I can put this in? portmgr. From the portmgr pages: Changes to bsd.port.mk are not the only commits that can have a drastic effect on the tree. We request that any such changes also be tested on

Re: what's the deal with portsmon? and beefy?

I have been working on it off and on the past 3 weeks. I do not have an ETA for the reworked codebase yet. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: The future of portmaster

On Thu, Feb 16, 2017 at 04:36:24PM -0500, Baho Utot wrote: > Oh no I am now banned as I use synth, whoa is me. This is overstating the matter. May we restrict ourselves to the technical problems/features of the various port maintainence tools, please? :-/ mcl

Re: Ports search last database update 2016-01-01

On Sat, Feb 18, 2017 at 09:18:12AM +0100, Kurt Jaeger wrote: > http://portsmon.freebsd.org/portoverview.py I maintain portsmon. I'll take a look at it. mcl ___ freebsd-ports@freebsd.org mailing list

Re: openjdk6-i386 not found

Do we even have the right to redistribute that? mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On Fri, Feb 10, 2017 at 08:17:31AM -0500, scratch65...@att.net wrote: > A good rule of thumb from industry in the case of major software > would be "forever", meaning until it's very unlikely that anyone > is still using it because of hardware obsolescence, etc. (Sigh.) And how many people do

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On Fri, Feb 10, 2017 at 11:02:41PM +0100, Michelle Sullivan wrote: > Or the last strong hold you have - the server owners - get so p**sed off in > reality they can't keep up with the OS updates that they migrate away... So we should give up on EFI, 4k drives, and SSD? mcl

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

On Sat, Feb 11, 2017 at 09:51:41AM +0100, Michelle Sullivan wrote: > Tell me What is the reason for me upgrading those few production > servers from 9.3 to 10/11?... bearing in mind the following: There isn't any ... oh, except for no new security updates. The flip side is the more

Re: The future of portmaster

I am glad to see that someone is taking on the work. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: HEADSUP: after r313194 on freebsd-current, lang/gcc ports require a rebuild

On Tue, Feb 28, 2017 at 11:24:27PM +0100, Ed Schouten wrote: > 2017-02-28 21:00 GMT+01:00 Konstantin Belousov : > > Ideally, ports should stop shipping mangled system includes, or even better, > > gcc stop doing fixincludes. > > Amen. Please let me know the magic wand you

Re: ${INSTALL_DATA} problems

On Fri, Sep 09, 2016 at 08:29:12AM +1000, Aristedes Maniatis wrote: > Maybe the Makefile language will become clearer to me one day, but > I've been using FreeBSD since 4.0 and it hasn't clicked yet. Don't worry, the FreeBSD ports framework does things with the Makefile language that was never

Re: Installing ports via pkg on 11 [ports-mgmt/synth only available for amd64 and i386 on FreeBSD]

On Sat, Sep 24, 2016 at 10:06:07PM +0200, Luciano Mannucci wrote: > Ah, no ada for the Powerpc... that I didn't know. May I ask why? No one has done the work to try to make the compiler work. Please see the website that John Marino (marino@) has for more information:

Re: dependency explosions

On Tue, Oct 04, 2016 at 10:21:30AM +1100, Greg 'groggy' Lehey wrote: > Is there a way to display these dependencies in a tree structure? http://portsmon.freebsd.org/portdependencytree.py?category=x11=kde4 It's slow because I do not store dependencies in the database, so it recalculates it on the

Re: Google Code as an upstream is gone

On Fri, Sep 30, 2016 at 02:51:07PM +0200, David Demelier wrote: > We should provide a longer expiration date by keeping distfiles to our > FreeBSD mirrors for a while until the upstream moves to somewhere else. My past experience looking into such things tells me that once this happens the

Re: openntpd-5.7p4_2,2 depends on libressl-2.2.6 ?!

On Wed, Oct 26, 2016 at 09:12:33PM +0100, Joe Holden wrote: > Yes, it is a ridiculous situation but since there appears to be zero > coordination between ports committers, probably expected. Thank you for making sure my motivation to work on fixing things stays at a nice, zero, level. You *do*

Re: misc/jive deleted

On Sat, Oct 22, 2016 at 05:46:15PM +0200, Julian H. Stacey wrote: > Censorship is offensive. Censor the offensive Censor: remove his/her commit > bit. IIUC correctly you will be removing more than one commit bit, but again, I cannot speak for those who made the decision. "Free Speech" means

Re: misc/jive deleted

On Sat, Oct 22, 2016 at 01:31:04PM +0200, Alphons van Werven wrote: > I'm still half waiting for someone with misguided delusions of moral > superiority to delete that port, thinking it's their decision to make > that FreeBSD must not enable people to display their system load as a > cartoon woman

Re: misc/jive deleted

On Sun, Oct 23, 2016 at 02:44:11AM +0200, Alphons van Werven wrote: > > > > Answering opposition/criticism with violence isn't exactly my style. So. If you say something that makes me want to plow my face into my hands, that's violence? Wow. mcl

Re: misc/sword should be removed

Thank you for your very nice troll. I was going to work on some FreeBSD stuff today but now I think I'll find something better to do. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To

Re: private ports and pkgs versioning

On Tue, Oct 18, 2016 at 08:49:06AM +0100, Matthew Seaman wrote: > Yes, there is a lot of useful stuff in the ports tree to support local > ports or even whole local categories of ports. I can't recall now how I > learned about all this stuff -- it may well have been just be a > combination of

Re: private ports and pkgs versioning

On Tue, Oct 18, 2016 at 02:52:34PM +0100, Matthew Seaman wrote: > Hmmm... looks like this is handled in the 30 or so lines starting at > line 1179 of bsd.port.mk Wouldn't the patch to ports/Makefile just be the following? .if exists(${.CURDIR}/Makefile.local) .include "${.CURDIR}/Makefile.local"

Re: misc/jive deleted

disclaimer: I wasn't the person who made the decision. This change became contentious after it was made; however, that discussion only occurred on internal mailing lists. The "pro" removal points: some of these terms are no longer acceptable in polite society, and far cross the line from humor

Re: misc/jive deleted

On Sun, Oct 23, 2016 at 03:56:07PM -0400, Mikhail T. wrote: > Technically, the only reason to remove a port is due to a failure to > build -- and that hasn't happened. Or: - expired, replaced by newer version - unfetchable - license does not allow anyone to package it - author requested(*)

Re: Fwd: [package - 93i386-quarterly][cad/freecad] Failed for FreeCAD-0.17.g20160907_1 in build

On Mon, Nov 21, 2016 at 09:40:58PM -0500, Pedro Giffuni wrote: > I am not even the port maintainer anymore and I still get these error > messages. In branches/2016Q4/cad/freecad/Makefile you still are :-) > Log URL: >

Re: really to pkg people

On Tue, Nov 29, 2016 at 01:21:44AM +0800, Julian Elischer wrote: > It's most disconcerting when a quarterly collection of packages disappears > and one has nowhere to get new packages that match all the ones out in the > field. I think this is more a question for clusteradm@ than for the ports

Re: Ports update submission for multiple ports?

Back before we had Bugzilla, I used to recommend separate submissions for each port. But Bugzilla gives us a little more flexibility on Cc:ing and tracking maintainers, so it is not as hard for us to deal with now. Having said that, I personally still have a slight preference for individual PRs.

Re: Binary for Ruby?

On Mon, Nov 21, 2016 at 01:23:28PM +1100, Dave Horsfall wrote: > Is a binary available for Ruby? http://pkg.freebsd.org/FreeBSD:9:i386/latest/All/ruby-2.2.6,1.txz http://pkg.freebsd.org/FreeBSD:9:i386/latest/All/ruby23-2.3.1_1,1.txz

Re: portsnap tardis

On Thu, Oct 13, 2016 at 04:58:56PM +0900, Randy Bush wrote: > Fetching snapshot tag from your-org.portsnap.freebsd.org... done. IIUC there was an outage on this server and it has been fixed. mcl ___ freebsd-ports@freebsd.org mailing list

Re: pkg: PRE-INSTALL script failed

Is this with pkg 1.9.0 or the just-issued 1.9.1? mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/mixmaster port issue

On Sat, Dec 10, 2016 at 08:16:11PM +, RW via freebsd-ports wrote: > what's the point of supporting backup servers in the ports makefiles > if a port is marked as BROKEN every time it's useful. We've learned from experience that otherwise the problem will never be fixed. mcl

Re: The ports collection has some serious issues

This is the sixth "top of thread" post. Could you please arrange to stop breaking email threading? Thanks. mcl ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: svn commit: r427110 - head/lang/gcc/files [does lang/gcc49 need such too?]

On Sun, Dec 11, 2016 at 02:59:36PM -0800, Mark Millard wrote: > I tend to have powerpc64 and powerpc patches because of my > experimenting with clang targeting them and that the standard > powerpc64 build does not boot PowerMac G5's reliably. Is that on 10, 11 or -current? On 10 I remember being

[CFD] changes to Handbook chapter on Ports

Executive summary: the chapter needed help, and still needs more. Full explanation: I have submitted https://reviews.freebsd.org/D9124 to add a section about ports-mgmt/synth, and a compare-and-contrast table for it and poudriere, portupgrade, and portmaster. I fully expect this section to be

Re: Ports' tips and gotchas

On Tue, Jan 03, 2017 at 06:16:26PM +0100, Vlad K. wrote: > However, what would be the best way to approach this via the FreeBSD wiki? > I'm sure that random wiki pages in various users' namespaces is not quite > the right thing to do. There currently are some ports Wiki pages but they're > all

<    1   2   3   4   5   6   >