On Tue, Jul 14, 2009 at 11:07:48AM -0700, Charlie Kester wrote:
Is the portstree updated before running these build tests?
The unbuildable ports script has errors. I have it on my list of things to
go look at.
mcl
___
freebsd-ports@freebsd.org
On Wed, Jul 22, 2009 at 12:21:12PM -0400, Wesley Shields wrote:
On Wed, Jul 22, 2009 at 11:25:24AM -0400, Mike Jakubik wrote:
Hi,
Could someone please commit these updates before the ports freeze comes
in? I don't think these maintainers are very active any more. I've been
running the
Done, thanks.
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
On Thu, Jul 23, 2009 at 07:37:27PM +0200, Martin Tournoij wrote:
I now know more than ever why I switched to OpenBSD.
FreeBSD people no longer seem to care about broken ports, or making people
who submit broken patches maintainers, or even replying to my messages.
First of all, I have to
On Tue, Aug 04, 2009 at 11:55:19AM -0400, Alex Goncharov wrote:
Wouldn't it be better for everybody if more people could commit the
changes in their ports themselves? (Subject to a commit-privilege
revocation on a substantial breakage anyplace).
IMHO: no. Too many people automatically update
On Tue, Aug 04, 2009 at 05:44:57PM -0400, Alex Goncharov wrote:
Could do more for the project -- but looks like nobody needs it. Oh,
well, I am not insisting.
Persistence is the name of the game. The more PRs you submit, the more
you are likely to attract the attention of the existing
On Sun, Aug 09, 2009 at 10:16:44AM +0200, Klaus Koch wrote:
as of 6th of August, there's a possible remote code execution exploit
known in both Sun JDK and JRE 6 Update 14 and earlier and Sun JDK
and JRE 5.0 Update 19 and earlier [...] I didn't get any notifications
with portaudit yet. Because
Done, thanks for all the help in the past.
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
OK, I've given it over to you and extended its life another few weeks.
Good luck :-)
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Wed, Sep 30, 2009 at 03:05:08PM +0400, Dmitry Marakasov wrote:
I've seen the license change too. I'm working on the port currently.
As a reminder, the last time this software was in the ports tree, the
developer threatened us with a lawsuit. This repeats what he has
previously done to
On Thu, Oct 01, 2009 at 03:45:46PM +0400, Dmitry Marakasov wrote:
Now it's LGPLv2.1 with the only restriction that this software may not
be significantly changed while being distributed as ion3.
I hate to replay this whole issue from the beginning, but apparently there
is no other way.
The
On Thu, Oct 01, 2009 at 02:58:23PM +0400, Dmitry Marakasov wrote:
No need to, if it works fine and there are no objections for it,
I'll commit it to the tree.
I insist that you not to commit it to the tree. See my other post.
mcl
___
Please see my other post about this port. Thanks.
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
On Fri, Oct 02, 2009 at 05:32:31PM +0400, Dmitry Marakasov wrote:
Do you honestly think the probability of Tuomo suing us is higher of,
say, me suing, well, us?
Yes. That is exactly what I am saying. And I believe reading the entire
thread when this first came up supports my claim.
mcl
You're blocking mail from FreeBSD.org, among others:
c...@kr.freebsd.org: host mail.kr.freebsd.org[210.118.94.73] said: 554 Service
unavailable; Client host [69.147.83.53] blocked using krrbl.or.kr (in reply
to RCPT TO command)
mcl
___
On Tue, Oct 06, 2009 at 12:06:08PM +0400, Alexander Bubnov wrote:
Why FreeBSD does not use pkgsrc of NetBSD project as default ports?
You're able to do so if you like -- FreeBSD is a supported pkgsrc
platform IIUC.
OTOH, there are some things FreeBSD ports are able to do that pkgsrc
can't (e.g.
On Mon, Nov 02, 2009 at 05:44:20PM -0800, Russell Jackson wrote:
The last commit to the port was after a maintainer timeout of 3+ months.
I've been running 0.25.0 for a while now internally. If nobody else is
maintaining the port, I'll submit what I have to update the official port.
I didn't
As an experiment, we never had a 'hard freeze' this release.
We're still in a mode where we are asking for no sweeping changes to be
committed until 8.0 is out the door, in case we have to do tag slips and
rebuilds to catch up with security problems.
mcl
On Tue, Nov 10, 2009 at 01:06:26PM -0500, Sean McAfee wrote:
What's the ports@ policy for things like this? I know I'm pretty peeved
that openntpd was pushed to 4.x, which requires 7.
In a perfect world, I'd prefer for someone to fix the newer port on 6.
However, it's fair to note that 6 is
On Wed, Nov 18, 2009 at 04:52:04AM +1100, Peter Jeremy wrote:
It is the maintainer's responsibility to update the port. If the
existing maintainer has vanished, you can take over maintainership by
submitting a PR that updates the port and changes the MAINTAINER line.
If the ports team are
On Mon, Nov 23, 2009 at 10:16:29PM -0800, Jim Pazarena wrote:
Is there any way of getting this rolled into the upcoming 8.0 Release ?
waaay too late.
mcl
___
freebsd-ports@freebsd.org mailing list
On Mon, Nov 23, 2009 at 09:05:46PM +0200, Aldis Berjoza wrote:
I and some other FreeBSD users are wondering why there are no
OpenOffice.org package available on FreeBSD Mirrors?
OpenOffice is one of our most complex packages, and, depending on which
package node it builds on, can take nearly a
On Thu, Nov 26, 2009 at 11:15:50AM -0800, Max Baker wrote:
Is there a maintainer for net-mgmt/netdisco?
nope, it's listed as po...@freebsd.org which is the place-holder
address (signifies unmaintained). So, it's ready for adoption :-)
mcl
___
On Tue, Dec 08, 2009 at 09:15:13AM -0300, oren.al...@gmail.com wrote:
For the last couple of days I have been following the pointyhat build
statistics provided at
http://pointyhat.freebsd.org/errorlogs/packagestats.html
Brave man :-) That's one I set up.
As seen on that page, the building
On Tue, Dec 08, 2009 at 04:58:30PM -0800, Doug Barton wrote:
In developing the package code for portmaster I used the 8-current
packages with good result (and in fact coded that into the script for
now). However as time goes on and more things change between 8-stable
and 9-current that
ok, I've marked it for deprecation early next year.
In general it's best to file PRs for things like this, so it doesn't just
get overlooked in all the mailing list traffic. Thanks.
mcl
___
freebsd-ports@freebsd.org mailing list
On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote:
The maintainer, ruby@, is aware of this; a check of the PR
database shows multiple open PRs, none critical but many serious
going back six months and more.
As an aside, the Severity and Priority fields have been so often abused
as to
On Thu, Dec 17, 2009 at 04:48:43PM +0100, Dominic Fandrey wrote:
A committer explained to me that he doesn't want to deal with SVN
snapshot based ports. Is that a common attitude and what should
I do to remedy this?
Well, the problem is that we (FreeBSD) can't guarantee whether the
contents of
On Fri, Dec 18, 2009 at 12:31:38PM +0100, Dominic Fandrey wrote:
But that's not different for any port. E.g. sysutils/bsdadminscripts is
all mine, I create the distfiles and maintain the port, their is no
guarantee that I don't do evil apart from me being quite certain that
I don't.
Sure
On Fri, Dec 18, 2009 at 01:43:20PM +0100, Dominic Fandrey wrote:
Are committers really supposed to read the code?
Yes.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail
On Fri, Dec 18, 2009 at 02:50:31PM +0100, Dominic Fandrey wrote:
So when I submitted ioquake3-1.36 I condemned some poor committer
to read 366609 lines of code?
We expect them to test-install the initial code to make sure it's
not malware.
We expect them to scan the diffs to make sure the
On Sat, Dec 19, 2009 at 04:02:31PM +0100, Dominic Fandrey wrote:
I don't see the wiggle room for anything spontaneously changing when
properly checksummed distfiles are involved.
Alright, then I misread it.
mcl
___
freebsd-ports@freebsd.org mailing
On Sun, Dec 20, 2009 at 08:25:08AM -0500, Jerry wrote:
OK, jylef...@freebsd.org is listed in the 'pkg-descr' file, although
apparently he no longer maintains the port. You might try contacting
them anyway.
Jean-Yves has not been active for over 2 years now.
(This is kind of why I don't like
It's maintained by po...@freebsd.org, which is the default entry that
indicates that it has no maintainer.
If you're interested in seeing it updated, the best thing to do is to
submit a PR to update it. The following article will get you started:
Hmm, looks like someone just went ahead and updated it, but the article
may still be of interest to you.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Tue, Jan 05, 2010 at 01:58:57PM -0800, Doug Barton wrote:
My understanding is that we've given up trying to produce packages for
openoffice on all branches.
I have no idea who told you this, but it is completely false.
mcl
___
On Fri, Jan 08, 2010 at 06:56:38PM +, freebsd-po...@coreland.ath.cx wrote:
I created the lang/gnat-gcc44 port a couple of months ago and have
worked to ensure that it works on 7/8 i386/x86_64. Unfortunately, there
won't be support for other platforms until somebody else decides to do
the
On Sun, Jan 10, 2010 at 07:50:19PM -0800, Rob Farmer wrote:
I submitted PR 142414 to update graphics/lcdtest and the PR was closed
with the message Committed. Thanks! but I don't see where it was
actually committed. Could someone take another look at this? Thanks.
It's in the latest checkout
On Wed, Jan 20, 2010 at 04:51:47PM +0100, Francisco de Borja López Río wrote:
I've tried to contact the maintainer of the openerp-server port, but
I've no reply
Hmm, his last commit was today ...
I've tried to add a PR using the web interface to send-pr but it didn't
allow me to add the
I'm not really sure whether people use these shortcuts, but just in case:
There are shorthand symlinks in the pub/FreeBSD/ports/arch directories
that are stale. I am going to change '7' to '8' in their targets:
pub/FreeBSD/ports/amd64/packages-stable currently points to
On Sat, Feb 06, 2010 at 03:53:57PM -0600, ajtiM wrote:
I don't know why is a rush for something which doesn't work?
All the individual package builds were tested on our 'clean' build
environment (pointyhat.freebsd.org). portmgr wouldn't have approved
the commit otherwise.
We can't test every
On Sat, Sep 21, 2013 at 10:40:09PM +0700, Victor Sudakov wrote:
Could you update the port please?
The best way to help with this is to file a PR; with the patches
(if you have already made them).
mcl
___
freebsd-ports@freebsd.org mailing list
On Mon, Sep 30, 2013 at 10:05:52PM -0300, William Grzybowski wrote:
Hi,
Due to the bureaucracy involved its always best if you file a pr
(send-pr(1)) reporting the issue. Unless a portmgr steps in to fix the
problem.
It may seem like bureaucracy to folks, but it's a deliberately chosen
On Wed, Oct 30, 2013 at 03:19:10PM +0100, Guido Falsi wrote:
First of all you can look here:
http://portscout.freebsd.org/po...@freebsd.org.html
This is a list of unmaintained ports, with highlight for the ones
needing to be updated.
Another tool is portsmon, which cross-references port
On Sun, Nov 17, 2013 at 08:51:38AM +0200, Kimmo Paasiala wrote:
The porter's handbook states that the package building logs and
errors would be found at http://pointyhat.freebsd.org/ but the site
is not working. Where are the package building logs now?
The porter's handbook is stale.
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
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 and
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) will
On Sun, Nov 04, 2007 at 12:45:34PM +0100, Michaël Grünewald wrote:
First, this is not really a new port, but a revival of a dead one. is
there specific issues with this?
No, just label it [new port], but put in the Description that it's
coming back from the Attic.
Second, the port version I
On Fri, Nov 09, 2007 at 03:05:47PM -0800, Mark D. Foster wrote:
Cricket is marked
IGNORE= uses a UID registered to another port
What is the proper fix?
Change it to use some UID that isn't yet listed in the Porter's
Handbook and send-pr the diff.
If you're not using whatever port
On Tue, Nov 20, 2007 at 09:37:47AM -0600, J. Porter Clark wrote:
How do you trace the dependencies? I have found this uncommonly
difficult.
make all-depends-list
make build-depends-list
make package-depends-list
make actual-package-depends
make run-depends-list
make
On Sunday 18 November 2007, Maho NAKATA wrote:
How about doing something more simple like:
.if ${OSVERSION} = 700042
USE_GCC=3.4
.endif
which works great in my situation.
I'd rather see USE_GCC set unconditionally, so that INDEX will
be the same on 6 and 7.
Is there any hope of
IMHO, octave-forge should be merged into octave itself,
and relese version of octave and corrsponding octave-forge is old.
I think this is a temporal situation. Once octave will be updated
octave-forge will also be updated, and I believe octave-forge
will be built with gcc42.
OK, in that
: ports/databases/virtuoso Makefile
ports/security/squidclam Makefile ports/www/havp Makefile
ports/x11-drivers/xf86-video-openchrome Makefile
Date: Saturday 24 November 2007
From: Mark Linimon [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
linimon 2007-11-25 01
I've been generating these locally but not uploading them. Now, they
are up-to-date. If you are interested in what the state of the packages
is on the various architectures, these pages will be of interest.
Of particular interest to ports committers is the new page
On Fri, Nov 30, 2007 at 07:50:02AM -0800, Jason C. Wells wrote:
It wouldn't surprise me if portmanager is hoping that KDE 4.0 will go
prime time real soon. That's my big conspiracy theory.
Occam's Razor would suggest that portmgr is simply trying to get the
combination of src + ports
On Sat, Dec 01, 2007 at 03:08:43AM -0800, David Southwell wrote:
I must say I am having difficulty understanding the policies applicable
during ports freeze.
I had hoped that http://www.freebsd.org/portmgr/qa.html and
http://www.freebsd.org/portmgr/implementation.html would have been clear
On Sat, Dec 01, 2007 at 10:37:45AM -0800, David Southwell wrote:
But the chances are that freebsd-7 would be better becasue the extra 2 months
would give more feedback and urgent if not almost immediate needs for 7.1
might be delayed.
We've already _given_ 7.0 an extra 2 months; fortunately,
On Sat, Dec 01, 2007 at 11:56:42AM -0600, Stephen Montgomery-Smith wrote:
These are all reasonably good suggestions for how to get around the ports
freeze. But they will come with a price, namely someone has to implement
these changes (which I guess one of you would do)
fwiw, one of the
On Sat, Dec 01, 2007 at 06:51:58AM -0800, David Southwell wrote:
Before I do so let me step outsiide the freebsd environment and ask what our
comments would be if MS$ were to announce that they were about to release an
upgrade to their operating system and until the new upgrade had been
On Sun, Dec 02, 2007 at 03:54:28AM +0100, Andreas Davour wrote:
I looked in the Makefile for mplayer but couldn't find any MAINTAINER.
$ cd multimedia/mplayer
$ make maintainer
[EMAIL PROTECTED]
Looks like it's maintained to me ...
mcl
___
He lost me around the these days, the horsepower to rebuild
ports is easily available. He clearly has not idea, whatsoever,
of what the current work is.
mcl
___
freebsd-ports@freebsd.org mailing list
On Tue, Dec 04, 2007 at 11:06:32PM -0800, Jason C. Wells wrote:
I seem to recall Jordan writing that the ports system was never
intended to last as long as it did. I think he said the same thing
about sysinstall.
He was probably correct in both cases. However, we have this userbase
thing to
Folks, don't reply any further to this thread. The packages are
in the process of being removed, no further software from this
author will be accepted, no more drama will be had. Nothing to
see here, move along.
mcl
___
freebsd-ports@freebsd.org
On Wed, Dec 12, 2007 at 08:25:17AM +, Tuomo Valkonen wrote:
On 2007-12-12, Mark Linimon [EMAIL PROTECTED] wrote:
=== NOTICE:
And this would also stop binary package from being generated
for the releases?
No, the release packages were already built. You see, part of
the problem
On Wed, Dec 12, 2007 at 08:47:03AM +, Tuomo Valkonen wrote:
I could make it GPLv3 and nagware at the same time.
Yes, and you could put on makeup, shave your armpits, put on a ballerina's
dress, and declare yourself Queen of Saturn And All Its Moons for all it
matters to FreeBSD now.
We can
On Wed, Dec 12, 2007 at 12:08:46PM +0200, Tuomo Valkonen wrote:
Do what the fuck you want as long as you don't piss me off.
I personally consider this to be the null set. No one but you
seems to be able to figure out what this is. It certainly doesn't
seem to consist of do whatever you want
On Wed, Dec 12, 2007 at 10:36:23AM +, Tuomo Valkonen wrote:
Big and powerful distros can [piss me off], easily.
Ah, that should let FreeBSD off the hook, then.
mcl
___
freebsd-ports@freebsd.org mailing list
On Wed, Dec 12, 2007 at 08:12:17PM -0600, Mark Linimon wrote:
http://mail-index.netbsd.org/tech-pkg/2007/10/28/.html
Anyone interested in this thread needs to go read that one first.
As well as http://www.archlinux.org/pipermail/tur-users/2007-April/004634.html,
which contains the history
On Wed, Dec 12, 2007 at 07:30:46PM -0500, Mikhail Teterin wrote:
I expect the port-removal to be initiated/done in an orderly fashion.
Claims of license violations absolutely trump any process requirements.
portmgr has the explicit task of keeping the Ports Collection in as
best a legal state as
It was pulled from Debian, as well:
http://packages.qa.debian.org/i/ion3/news/20070310T233909Z.html
As far as I'm concerned, the matter is closed. When 4 different* OS groups
come to the same conclusion, I think there's not much else to say.
mcl
* pkgsrc, ArchLinux, Debian, and now FreeBSD
On Thu, Dec 13, 2007 at 07:43:36AM +, Tuomo Valkonen wrote:
On 2007-12-13, Mark Linimon [EMAIL PROTECTED] wrote:
Further, note that my initial commit tried to do this, and I asked the
author if it was acceptable. It was clear from his reply that it was
not -- especially considering
On Thu, Dec 13, 2007 at 02:48:07AM -0800, Jeremy Chadwick wrote:
I believe Mark removed the source tarball from the master FreeBSD FTP
server, and very likely removed the binary packages as well.
Correct.
mcl
___
freebsd-ports@freebsd.org mailing
On Thu, Dec 13, 2007 at 11:42:53AM +0100, Philip Paeps wrote:
Anyway. How does portmgr feel about this? Aye or nay?
I do not yet believe that it is possible to meet Tuomo's interpretation
of his license without his prior review of every possible patch, and I'm
not willing to obligate the
On Thu, Dec 13, 2007 at 09:23:24AM -0500, Mikhail Teterin wrote:
No, not impossible -- getting stuff out from the Attic is doable. But more
difficult (possibly involving contacting repo-meisters, etc.)
Wrong. You do cvs add, cvs com.
Any claims of license violations -- which, according to
On Thu, Dec 13, 2007 at 02:43:07PM +, Tuomo Valkonen wrote:
And at least where I come from, contracts are legally enforceable,
even if they're only oral ones
You clearly don't come from the US, where oral contracts are not
germane in business law. What's written down in the license is the
On Fri, Dec 14, 2007 at 07:51:14PM -0500, Garance A Drosehn wrote:
At 10:08 AM -0600 12/14/07, Paul Schmehl wrote:
SInce I've already killfiled Aryeh,
I guess we should all killfile you, too.
Can we please just stop the meta-thread now and go back to working on all
the myriad things that
On Mon, Dec 17, 2007 at 11:02:45AM +0900, Hiroki Sato wrote:
Do you think splitting it to small packages will be a big problem?
That many ports would create a significant impact on the build systems,
especially, sparc64, which is not keeping up at all as it is.
mcl
On Mon, Dec 17, 2007 at 12:59:54PM -0300, Alejandro Pulver wrote:
if not already done, AFAIK tinderbox has an option to run parallel
builds, but don't know about pointyhat) using multiple processors.
pointyhat is actually the dispatch machine. It does not actually
build packages.
The current
On Mon, Dec 17, 2007 at 11:54:45PM -0300, Alejandro Pulver wrote:
I remember some of my ports failed on ia64 (some time ago), what
happened to it/them?
There are 2 ia64 build machines, each of which has been upgraded to
7.0. However, neither is able to build packages at this time, so
until
On Thu, Dec 20, 2007 at 08:36:32PM -0500, Chuck Robey wrote:
Back last time I was last active,Satoshi Asami was the Portsmeister. I
dunno if that term is used anymore, but I need to find out if one person is in
charge of ports, or if it's a group of folks, and whichever it is, what their
On Fri, Dec 21, 2007 at 10:42:50PM +0300, Max Brazhnikov wrote:
I've submitted several pr (ports/117807, ports/118269, ports/118502) to
fix/update ports which are maintained by @freebsd.org people.
Of these, the last 2 came in during the time that the ports tree was
frozen in preparation for
Please see http://wiki.freebsd.org/Sparc64Packages for a writeup on where
we are with respect to sparc64 packages, from portmgr's perspective.
Quick summary: we're far behind where we are on i386. In particular, we
can't build KDE anywhere at the moment, which affects the release package
set.
On Fri, Jan 11, 2008 at 06:40:35PM +0100, Guido Falsi wrote:
I think that too much formalization in the porting rules would harm the
system.
That seems to have been the community consensus in the past.
Nevertheless, the PH could use some improvement. Most of what I've
tried to put in there
On Fri, Jan 11, 2008 at 11:10:45AM -0600, Paul Schmehl wrote:
The porters handbook seems written from the standpoint of a guide more
than a manual.
That's something that I was going to work on, um, last year :-)
We need both. Right now we have this hybrid which isn't a completely
satisfactory
On Fri, Jan 11, 2008 at 09:24:36PM -0800, Doug Barton wrote:
If you're not keen to learn the SGML there are people who can help
you with that, but coming up with good content that covers the needs
of people like you can (somewhat ironically) be done most easily by
people like you. I hope this
It's in there towards the end:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-deprecated.html
You can just file a PR adding the DEPRECATED and EXPIRATION_DATE lines.
The only reason we do this step is to provide warning for any existing
users.
mcl
On Tue, Jan 29, 2008 at 08:30:03PM +0100, GP wrote:
I'm just wondering how log it usually takes from you submits a new port, to
something happens?
Everything is done by volunteers, so the answer is, it depends.
As I check there is a backlog of 980 port PRs. You can get an idea of the
On Sun, Feb 03, 2008 at 02:31:48PM -0500, Bill Moran wrote:
$ uname -a
FreeBSD monster 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #2: Sun Dec 30 11:59:30
EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
$ pkg_info | grep lyx
lyx-1.5.3 Document processor interfaced with
On Fri, Feb 08, 2008 at 11:02:57AM -0800, Gregory W. MacPherson wrote:
It would be nice if the owners of these various ports would update their
Makefiles and Configuration scripts to check for the existence of the
other ports and (gasp) actually build the missing dependencies). While
some
On Sat, Feb 23, 2008 at 10:17:04PM -0800, comperr wrote:
What you package a port properly (with the shell archive and such)
what is the usual response time you get until a comitter sees it and
commits it?
There isn't a usual response time. It can run from a few days to a
number of months. We
On Mon, Mar 03, 2008 at 09:12:37AM -0800, pjd wrote:
With me the JDK ports stop and demand I manually download the files, which
is even more irritating
Given Sun's licensing requirements, what is your suggestion?
mcl
___
freebsd-ports@freebsd.org
Both ports were updated on Jan 03 with patches that will (hopefully)
fix them on sparc64 with with PORTREVISIONs bumped, still portsmon
shows builds failed on Feb 25, and those are old versions of ports.
Because sparc64-7 was (is) still, during that time, doing nothing
but building the 7.0
On Wed, Mar 05, 2008 at 04:22:28PM +0100, Nikola Lečić wrote:
(BTW, are/were there ideas of implementing something similar in Ports
Collection?)
Yes, I think we are at the point of needing to implement this. I hope
we can use what pkgsrc has (the concepts if not the code); it sounds as
though
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-deprecated.html
(I'll admit this page is not the easiest to find)
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Tue, Apr 15, 2008 at 09:24:43AM +0800, John/SML wrote:
Then, I think the appropriate way to keep up with port updates is to
upgrade from FreeBSD 4.11 to FreeBSD 7. However, it is possible to use the
build world method to upgrade from 4.11 to 7, or I have to use the
binary upgrade method
On Mon, Apr 28, 2008 at 02:42:56PM -0700, Xin LI wrote:
To make it short - how often pointyhat would do a full build?
A full (from scratch, with latest src changes) build is not done very often.
We guarantee we do it before release time; there are other times, as well,
(at least on i386/amd64).
On Mon, Apr 28, 2008 at 06:41:30PM -0700, Xin LI wrote:
So does it imply that pointyhat's -CURRENT would (slightly) behind the
current development?
Yes, it takes some amount of time to upgrade everything.
Is there any way to know which __FreeBSDversion the current build is
running against?
On Sat, Jan 12, 2013 at 09:57:16AM -0600, Bryan Drewery wrote:
Yes pkgng is not default today, but it will be someday
IIUC pkgng is default on -CURRENT.
mcl
___
freebsd-ports@freebsd.org mailing list
On Sun, Jan 13, 2013 at 04:02:13PM +, RW wrote:
FreeBSD doesn't exactly announce deprecation on display in the bottom
of a locked filing cabinet stuck in a disused lavatory with a sign on the
door saying Beware of The Leopard but it's pretty close.
See, e.g.,
101 - 200 of 545 matches
Mail list logo
