> So, is it time to mark it as obsolete and pull it from ports?
Yep, sounds like. Just send-pr it and it will get assigned to the
maintainer (or this list if it's "maintained" by [EMAIL PROTECTED])
mcl
___
freebsd-ports@freebsd.org mailing list
http://
The output from each port's "make describe" is documented at the
"describe" target in:
http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk
This is changed to a different format (a historical bug, too late to fix
now because of POLA) via "make index" from ports/Makefile by the following
scr
On Tue, May 08, 2007 at 07:49:02AM +0200, [LoN]Kamikaze wrote:
> Submit a PR and request a maintainer timeout. This will take a long time,
> but it's the only way.
"long time" = "2 weeks"
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freeb
On Tue, May 08, 2007 at 10:23:43AM +0200, [LoN]Kamikaze wrote:
> The last time I requested a maintainer time out it was something like
> two months.
I have been much more active in the last few months on enforcing the
maintainer-timeouts.
If you are having problems, please email portmgr@ directly
On Tue, May 08, 2007 at 11:58:43AM -0500, Sam Stein wrote:
> I've already submitted a pr with the update; before I read about the
> maintainer timeout; should I just wait it out a while, and if nothing
> happens, request one? Or do it right away?
Just wait it out for a while. At the moment, we're
On Thu, May 10, 2007 at 10:48:30AM +1000, [EMAIL PROTECTED] wrote:
> The latest release of PHP is out (as at May 3) and I'm just wondering if
> there's a schedule for updating the port - this release corrects some not
> insignificant security vulnerabilities.
We are in an unusual ports freeze to d
On Thu, May 10, 2007 at 10:00:06AM +0200, [EMAIL PROTECTED] wrote:
> Do you know that PHP 5.2.1 has a "Security Enhancements and Fixes in
> PHP 5.2.2 and PHP 4.4.7" as reported on www.php.net? When will be
> available the PHP 5.2.2 in the ports?
Please go read the archives of this mailing list ove
On Sat, May 19, 2007 at 01:51:02PM -0700, Garrett Cooper wrote:
> Wouldn't it be sufficient to force major component testers (in this
> case Xorg 7.2) to use periodic snapshots of the ports tree (possibly CVS
> branching), while allowing continued development in the ports tree?
In this particula
On Sun, May 20, 2007 at 12:47:07AM +0200, Andreas Gehrke wrote:
> when PHP 5.2.2 will be available for install via the ports collection.
There has been a global freeze to enable the xorg7.2 import and the
move from X11BASE to LOCALBASE. This has delayed the php update. We
hope to fix php soon.
On Mon, May 21, 2007 at 09:15:44AM +0200, Hans Lambermont wrote:
> Do you happen to have a portmaster version of UPDATING:20070519 users of
> x11/xorg ?
I think he may have gone to sleep already, so I'll step in and answer
for him that he is working on it and may have a patch shortly.
mcl
___
On Tue, May 22, 2007 at 02:20:43PM +0200, Dag-Erling Smørgrav wrote:
> Then you need to run a kernel that corresponds to the newest userland
> the tinderbox wants to run - or from a different perspective, configure
> the tinderbox to only run userlands as old as or older than your kernel.
Yes, tha
On Tue, May 22, 2007 at 05:34:32PM +0400, Andrew Pantyukhin wrote:
> A seemingly better way may be to make these system vars
> available in make by default.
Doesn't help anyone who runs -RELEASE, so a non-starter.
mcl
___
freebsd-ports@freebsd.org maili
Synopsis: [PATCH] security/pam_per_user conflicts with security/courier-authlib
Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu May 24 11:15:30 UTC 2007
Responsible-Changed-Why:
Fix assignment.
http://www.freebsd.org/cg
On Thu, May 24, 2007 at 09:21:09AM -0400, Robert Huff wrote:
> I'm having the same issue. Investigating a little reveals the
> size as listed in distinfo as 190172 and the size of the downloaded
> tarball as ~7200.
Generally mismatches like this are returning HTML pages instead of the
desired bin
On Thu, May 24, 2007 at 12:02:39PM -0700, Walter Ian Kaye wrote:
> All right, who released my email address to spammers?
The mailing lists are public and mirrored all over the world. It's too
late for that address, sorry.
mcl
___
freebsd-ports@freebsd.
If you use 'make update', the default method is going to become portsnap.
Currently, if you do not define one of the Makevars PORTSNAP_UPDATE,
SUP_UPDATE, or CVS_UPDATE first, the code just complains at you and
does nothing.
This is one less thing that has to be set by default by an administrator.
On Mon, May 28, 2007 at 12:15:28AM +0200, Michel Talon wrote:
> To gain some performance, a first idea would be to simplify
> bsd.ports.mk. I am convinced that a substantial part of the 4000 lines
> are historical crap which serve no useful purpose.
11272 of LOC in bsd.*.mk, but who's counting.
>
On Mon, May 28, 2007 at 10:16:11AM +1000, Edwin Groothuis wrote:
> It has been discussed on IRC, and I'm pretty sure that flz@ has
> been thinking about it during his sweat-shop-job. My opinion is:
> let's do the upgrade to 7.2 and the new framework first, then see
> what can be done about OPTIONiz
> I can't build index after recent update of ports via portsnap:
>
> wait..astk-client-1.5.0.1_2: "/usr/ports/shells/bash2" non-existent --
> dependency list incomplete
As a reminder to committers, when removing stale ports, you also have to
check the _optional_ dependencies in port Makefiles (ye
On Thu, Jun 07, 2007 at 06:16:38PM +0200, Daniel Stefan Haischt wrote:
> attached you will find an modified wzdftpd port. Included are just
> changed files.
fwiw, if you're going to Cc: to the list, you may as well just file it
as a PR and then it will be auto-assigned to novel. Postings to the l
On Sat, Jun 09, 2007 at 07:48:44AM +0200, [LoN]Kamikaze wrote:
> So you better file a PR to step back from maintainership, so that volunteers
> don't have to wait for a time out.
Already taken care of.
mcl
___
freebsd-ports@freebsd.org mailing list
http
On Tue, Jun 12, 2007 at 10:55:42AM +0700, Dede NURMANSYAH wrote:
> Do you have a plan to port zabbix 1.4 into port current? Because many
> improvement since 1.1.x of zabbix release.
Since the port is unmaintained (just assigned to the mailing list),
there is no "plan". It will take someone who wa
On Sat, Jun 16, 2007 at 07:50:14AM -0500, Jack Stone wrote:
> You could simply edit the Makefile in the samba port and reset the version
> shown at the top to the old version.
>
> Then, delete distinfo
> Then 'make makesum'
> Then 'make install clean'
>
> If the old port still remains in your /u
On Sun, Jun 17, 2007 at 12:15:16AM -0600, M. Warner Losh wrote:
> I want a list of all the ports in /usr/ports that install kernel modules.
IIRC they're all in misc/. Let me see if I can come up with a quick list.
mcl
___
freebsd-ports@freebsd.org mail
On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote:
> I'd kinda hoped there was a pseudo category that I could key off of.
Kinda sounds like there should be.
Here's my list so far:
audio/aureal-kmod
audio/emu10kx
comms/hcfmdm
comms/ixj
comms/ltmdm
comms/uticom
comms/vpb-driver
graphi
ok, good luck on getting caught up.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Thu, Jun 28, 2007 at 12:55:37PM +0200, Tim Rijavec wrote:
> can you build package that can be installed using FreeBSD ports for
> application ChartDirector found at http://www.advsofteng.com/
The right place to ask is freebsd-ports@FreeBSD.org (Cc:ed). Checking,
no one has yet created a port
On Thu, Jun 28, 2007 at 06:38:24AM -0700, David Southwell wrote:
> There is a difficulty when posting PR's when a large debug file is needed to
> be posted to the PR as an attachment.
Do you mean, via the web form or via send-pr(1)? The latter has a limit
of 500k, via the FreeBSD.org email syste
On Mon, Jul 02, 2007 at 12:34:20PM +0200, Tim Rijavec wrote:
> can you add this package for ChartDirector for php to FreeBSD ports?
> that can be found at http://www.freebsd.org/ports/master-index.html
Please use send-pr to submit this so that it won't just get lost in the
mailing list traffic.
On Tue, Jul 03, 2007 at 11:19:04PM +0700, budsz wrote:
> So the best way I should upgrade my system to FreeBSD 6.X series?,
Yes, that is what we have been recommending for some time now.
> BTW which one:
>
> "tag=RELEASE_4_EOL" or "tag=RELEASE_4" ?, I've already read in
> handbook and didn't fin
I went ahead and fixed it.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I have just updated portsmon to the most recent development code. Most of
this code has to do with the ability to create dependency graphs of failed
or broken ports, and is not yet totally automated; thus, it is not (yet)
visible to users. Other code has to do with internal schema changes.
The m
On Fri, Jul 20, 2007 at 05:11:27PM +0200, Michel Talon wrote:
> The only relevant info for determining what to install or build
> previously is RUN_DEPENDS and BUILD_DEPENDS. Everything else is garbage.
The pointyhat error logs would tend to indicate that this isn't correct.
mcl
_
On Fri, Jul 20, 2007 at 12:40:02PM -0700, [EMAIL PROTECTED] wrote:
> >> the INDEX files -- so many that I think that items common to both
> >> build_deps and run_deps should be isolated and put into a new category
> >> called 'common_deps':
> >
> >How will this benefit us?
> >
> >Doug
>
> Reduce a
On Fri, Jul 20, 2007 at 08:58:55AM -0400, Bill Moran wrote:
> Why? Is there a legitimate reason why the fetch process refuses to
> download this?
The intention of the logic is to warn a user, as soon as possible, that
they are spending time on something that will wind up being IGNOREd if
it is in
On Fri, Jul 20, 2007 at 04:07:49PM -0400, Bill Moran wrote:
> Even better would be for make to realize that it's only doing the
> fetching, and do it anyway.
That still doesn't help with the problem of a user who starts a 10MB
download that won't work on his architecture or OS release. The code
i
I assume that you've already emailed the person? If so, sending email
to portmgr@ is the right way to go. We'll attempt to find out if the
person is busy/on vacation/overloaded/etc.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.or
I'm actually doing a slight superset by looking at dependent ports
of (ignore/broken/forbidden/failed) ports, now that I have updated the
graph and can "see" it better.
It sounds like people are already working on the misc/compat3x dependents.
Most of these ports are antiques.
IMHO sysutils/eject
On Mon, Jul 23, 2007 at 11:40:13AM -0400, Tuc at T-B-O-H.NET wrote:
> I went back to the EOL branch, got the devel/make, installed it.
> Went back to the current state, and still had the issue.
I vaguely recall that right as we tagged the tree as EOL, one of the ports
changed underneath us and bro
In general the way we want to assign maintainership is in conjunction
with a port update/fix. Please submit anything that you come up with
via GNATS.
Even if in the meantime the port gets deleted, it can easily be brought
back from the Attic.
Thanks for volunteering to help.
mcl
___
On Fri, Jul 27, 2007 at 12:39:51PM +0530, Alagarsamy A wrote:
> can you please update it to latest version 0.80
> (http://nsc-gothix.sourceforge.net/) ?
ports@ is the "default" maintainer. No update will happen until someone
(you?) submits a PR for it.
mcl
__
On Thu, Jul 26, 2007 at 04:27:37PM -0700, Kurt Abahar wrote:
> However, I don't know how to get a hold of this "lag
> time." Is it a few days, a few weeks or ... ?
You can get an _idea_ of the degree of the lag via the following URL:
http://pointyhat.freebsd.org/errorlogs/packagestats.html
The
On Wed, Aug 01, 2007 at 03:17:24PM +0200, Mark Evenson wrote:
> Which I would do but the [FreeBSD Bugs database][1] seems to not be
> returning any matches to queries
Seems to be working fine for me now. However, I've seen a 'no PRs found'
page to be displayed sometimes, possibly due to some int
On Sat, Aug 04, 2007 at 06:01:48PM -0700, Doug Barton wrote:
> The following line was placed first in the file, instead of in
> chronological order. Is there a reason that it needs to be first?
This is a bug. Fixed.
mcl
___
freebsd-ports@freebsd.org ma
On Sun, Aug 05, 2007 at 09:29:03AM -0700, Doug Barton wrote:
> Thanks! I forgot to include in my original message that this is
> important because some tools (like portmaster)
and portsmon
> rely on being able to parse the file in chronological order.
__
These reports deal with package failures, adding together all packages
that are intentionally not made, packages that fail, and all the packages
that depend on them.
Initially I generated these as graphs via GraphViz. However, the
resulting images are so large that they take minutes to display on
On Sun, Sep 02, 2007 at 01:50:36AM +0200, Nils Vogels wrote:
> Since a little while, Debian has been using a popularity contest, that
> sends anonymous usage details of various packages that Debian users have
> installed.
See sysutils/bsdstats. It apparently has not yet been extended to
ports/pac
The refactoring that gabor has done to recreate bsd.perl.mk will be
imported soon, along with the many ports that it simplifies. Due to
the size of the patch, I expect there to be collisions that I will have
to adjust as I go, so expect the tree to be broken briefly while I work
through the checki
This should fix the remaining perl-related problems that people were seeing,
each related to ports that conditionally included perl.
The only remaining regressions that I can't yet explain are the following:
*/fpc-* fail to compile due some kind of flag failure. (They work on
my 6.2 machin
Nothing has changed in the port, but this is showing up on both 5 and
5-exp now. Any ideas?
The offending item is the extra space after '/usr/local/lib':
mkdir -p /usr/local/lib /tcl8.4/tgraph1.0
cp ../../all/pkgIndex.tcl /usr/local/lib /tcl8.4/tgraph1.0
cp: /usr/local/lib is a directory (
Despite the fact that this was tested on the cluster, this upgrade has
failed. Please hold off upgrading your ports tree until we can figure
out what the problem is. Thanks.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailma
On Sat, Oct 06, 2007 at 05:40:05PM +0200, Max Laier wrote:
> On Sunday 30 September 2007, Mark Linimon wrote:
> > Despite the fact that this was tested on the cluster, this upgrade has
> > failed. Please hold off upgrading your ports tree until we can figure
> > out what th
(For those who are not familiar with the FreeBSD Ports Monitoring System,
or portsmon, that I wrote and maintain, you'll find more information at
portsmon.freebsd.org.)
To get ready for the 7.0 release, I've switched its model of the "default"
ports build environment from i386-6 to i386-7. This m
When we upgraded the machine that hosts these reports, we missed some
files, and the reports came out null. I am currently working on testing
the corrected script. While I'm working on it, I'm going to make a few
tweaks. Let me know if you see anything odd in the results.
mcl
__
The best thing to do is to send individual PRs for these ports, so that
they may be assigned to the maintainers. The mailing lists are so noisy
that things like this tend to just get lost.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.free
On Tue, Oct 30, 2007 at 09:54:54AM +0100, [LoN]Kamikaze wrote:
> I hope that when the freeze comes (wasn't that supposed to happen today?) the
> maintainer updates from before the freeze will still get committed.
No, the idea is that during the freeze period we turn our attention to
fixing bugs an
On Tue, Oct 30, 2007 at 11:35:48PM +0100, [LoN]Kamikaze wrote:
> I put a lot of effort to get the release done (4 days) before the freeze. So
> it's kind of frustrating that it doesn't get in.
I sympathize, but if we let one update in, it is very difficult to not let
them all in. We (portmgr) wil
On Mon, Jun 09, 2014 at 08:20:52PM +0200, Eric Masson wrote:
> I don't use lpr-wrapper anymore, it seems to me that lpr-wrapper & psdim
> have been superseded by P. Selinger's upprint :
> http://www.mathstat.dal.ca/~selinger/upprint/
>
> Thanks for resetting maintainer, please.
Done, thanks.
mcl
On Tue, Jun 10, 2014 at 04:53:17PM +1000, Dylan Leigh wrote:
> Don't know anything about staging yet but I will take maintainership
> and do it if noone else is willing to save the port.
If you're not familiar with port maintainership, here are the best
places to start:
http://www.freebsd.org/d
On Fri, Jun 13, 2014 at 09:35:53AM +0900, oyaaji wrote:
> Dear Sir/Madam,
>
> I have received following e-mail.
> However I am not a port maintainer and never was.
Apparently this was sent to a mailing list:
> To: v...@freebsd.org
mcl
___
freebsd-port
On Sat, Jun 21, 2014 at 12:02:32PM -0500, Pedro Giffuni wrote:
> This is a problem with the Apache POI port but it is also an issue
> with a potential Apache hadoop update: apparently our cluster
> doesn't like ports that download stuff as part of their build
s/doesn't like/doesn't allow/
This is
On Wed, Jul 02, 2014 at 07:43:17PM +0200, Daniel Ryslink wrote:
> I was quite seriously ill for some time, and I have only now noticed
> these messages. I am the maintainer of the games/gnarr port.
Please take care of yourself. Fixing ports should be secondary.
mcl
__
On Fri, Jul 04, 2014 at 07:00:00PM -0600, Mike Brown wrote:
> After starting down this road, you may decide it's less of an ordeal just to
> write something yourself and put it up on your own blog. :/
There are those of us who will do our best to pick up changes and run with
them.
mcl
__
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.
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:
http://portsmon.freebsd
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
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
http://lis
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
http
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
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
_
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 i
Thanks to the various folks in this thread for reminding me why I
stepped down from portmgr.
I really don't have the heart these days to argue with people.
Y'all have fun. I won't be contributing any more to this thread.
mcl
___
freebsd-ports@freebsd.
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
th
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 int
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:
http://www.dragonlace.net
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 underly
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&portname=kde4
It's slow because I do not store dependencies in the database, so it
recalculates i
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
https://lists.f
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"
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 read
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"
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 to
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
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 _you
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
___
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 unsubscribe,
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
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* kn
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.
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
http://pkg.freebsd.org/FreeBSD:9:amd64/latest/All/ruby-2.2.6,1.tx
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:
> http://beefy4.nyi.freebsd.org/data/93i386-quarterly/426753/logs/FreeCAD
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 tea
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
__
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
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 "freebsd
On Mon, Dec 19, 2016 at 07:07:06PM -0600, John Marino wrote:
> It's a natural reaction to stop attempting to contribute when previous
> contributions don't get "attention they deserve".
Which some people (including me) see as odds with:
> the impression that portmaster is officially recommended [
On Thu, Dec 22, 2016 at 01:04:22PM +0100, René Ladan wrote:
> Please join me in welcoming Adam and Mark.
Congratulations guys.
mcl
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
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 over
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 co
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 "freebsd-
401 - 500 of 615 matches
Mail list logo
