On Sat, Mar 03, 2012 at 09:08:28PM +0100, Nomen Nescio wrote:
> Thanks mcl. I am off on other things for now but I will file PRs next time
> I come across something. In the past I have emailed the port maintainer and
> the answer is usually "yeah I know". After a few of those I thought filing
> PRs
Thanks mcl. I am off on other things for now but I will file PRs next time
I come across something. In the past I have emailed the port maintainer and
the answer is usually "yeah I know". After a few of those I thought filing
PRs is a waste of time considering the maintainer doesn't seem to care.
Yeah, I've been trying to prioritize some -exps that are blocking
other people right now. I know there's many more :-)
mcl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail
On 02/03/2012 16:45, Mark Linimon wrote:
>> Other ports aren't supported on certain target architectures but the build
>> > doesn't tell you that until after it has run for a couple of hours
> Those are also bugs. Please send PRs for those, as well. I am particularly
> concerned about amd64 in t
On Fri, Mar 02, 2012 at 03:35:24PM +0100, Nomen Nescio wrote:
> If you use [!i386] you are likely to find problems with ports and
> this gets amplified if you use nonstandard (read stuff not everybody uses)
> ports.
Fair enough.
> I have found several ports broken for many releases in a row.
The
