[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: pkgsrc/cross/mingw-binutils
John Marino <netbsd%marino.st@localhost> writes:
> Everybody is tired of this. This is my last response on the topic.
> On 10/10/2012 00:10, Aleksej Saushev wrote:
>> It is a separate project already,
> It's joined at the hip with NetBSD the OS. No point in denying
> that, this very topic about spinning it off came up recently
> again. (and was blown off again)
>> but that doesn't mean that DragonFly
>> must be treated as system no. 1 and all others ignored.
> So somehow you changed "stop disparaging other platforms" into
> "I treat DragonFly as #1 system". That's deflection.
> Supporting GCC 4.7 is not good for DragonFly, it's good for
> pkgsrc. NetBSD will never have GCC 4.7 in base? ever?
Yes, it is quite possible that NetBSD will never have GCC 4.7 in base.
Just like FreeBSD and Darwin.
>> It doesn't matter if it is days or years. It still doesn't make Debian
>> platform no. 1 for pkgsrc. It doesn't make GCC 4.1 obsolete either,
>> whether you like it or not.
> Actually, by any reasonably measure, GCC 4.1 is long obsolete.
Here's where you prefer to ignore the reality.
By any reasonable measure GCC 4.1 is not obsolete and thus should be supported.
> I am not saying 4.1 shouldn't be supported by pkgsrc. However,
> I will ask if there are written policies about what is
> supported? Do you cut it off at 2.95? 3.0? 3.4? 4.0? 4.1?
3.4 until Solaris, which is platform no. 2 for pkgsrc, completes its transition.
> If this isn't written down, then there's no policy violation.
If it isn't written down, it doesn't mean that it doesn't exist.
> I've heard that the directive to support NetBSD 4.0 disappears
> when NetBSD 6 is released. What's the oldest netBSD 5.0
> compiler? Obviously it ignores every other Operating System but
> at least it's a measuring stick to understand what functionality
> needs to be protected. Defaulting to NetBSD 2.0 capabilities
> over something more recent is debatable.
NetBSD 4.1 is still there in field, Solaris 10 is still there in field,
CentOS 5 is still there in field. While pkgsrc is not a conservation
project, it isn't experimental project either.
>> Have you ever looked at pkgsrc/mk/bsd.hacks.mk and pkgsrc/mk/compiler/gcc.mk?
>> If not, take a look at it and stop rolling crude uncontrolled hacks again
>> and again.
>> It is a separate project that has its own rules which differ from DragonFly.
> Yes, I added a new compiler to gcc.mk. And?
> I interpret your response as declining to offer me anything useful.
If you do want to introduce dirty hacks to appease your compiler, do it
Make them depend on compiler version rather than ignore all warnings altogether
for any other user.
Main Index |
Thread Index |