Re: Updating CUPS
On Wed, 25 Dec 2013 09:14:55 +0100, Matthias Andree stated:
Jerry je...@seibercom.net schrieb:
The ports latest version of CUPS is 1.5.4; however version 1.7.0 has
been out since 10/24/13. Is there any possibility that the latest
version will make it into the ports system soon?
Careful with what you are asking for, have you checked the upstream
change logs? 1.6 already broke some aspects of compatibility
massively w.r.t. distributed printing or differing CUPS versions in
your LAN.
Well, almost any updated software has the potential to break something,
CUPS being no exception. However, those cases are not the norm and the
fact that in a few edge cases problems have been discovered is not a
sound reason for unilaterally failing to include the new version in the
posts system. There have been numerous cases where a new version of a
port was introduced into the system. In many of those cases workarounds
were introduced to allow the user to continue with the older version or
update to the newer one. I fail to see why that would not be acceptable
in this instance. In any case, how do you propose to find problems with
a new product if it is not tested in a real environment? In a worse
case scenario, a new port, perhaps cups-devel could be created.
--
Jerry
{Please don't CC me. I am on the list.}
___
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: Updating CUPS
On 12/26/2013 12:54, Jerry wrote: On Wed, 25 Dec 2013 09:14:55 +0100, Matthias Andree stated: Jerry je...@seibercom.net schrieb: The ports latest version of CUPS is 1.5.4; however version 1.7.0 has been out since 10/24/13. Is there any possibility that the latest version will make it into the ports system soon? Careful with what you are asking for, have you checked the upstream change logs? 1.6 already broke some aspects of compatibility massively w.r.t. distributed printing or differing CUPS versions in your LAN. Well, almost any updated software has the potential to break something, CUPS being no exception. However, those cases are not the norm and the fact that in a few edge cases problems have been discovered is not a sound reason for unilaterally failing to include the new version in the posts system. There have been numerous cases where a new version of a port was introduced into the system. In many of those cases workarounds were introduced to allow the user to continue with the older version or update to the newer one. I fail to see why that would not be acceptable in this instance. In any case, how do you propose to find problems with a new product if it is not tested in a real environment? In a worse case scenario, a new port, perhaps cups-devel could be created. Maybe rather than asking where is it? you should instead submit a PR with poudriere-tested patches that brings cups up to the new version? Until last week when bsam changed the MAINTAINER field in cups*, all the cups ports didn't even have a maintainer, so I don't know who you expect to do this work. PRs with patches have a greater chance of success that pinging the mail list and telling nobody-in-particular to spend their volunteer time on something specific... John ___ 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: Updating CUPS
Jerry je...@seibercom.net schrieb:
On Wed, 25 Dec 2013 09:14:55 +0100, Matthias Andree stated:
Jerry je...@seibercom.net schrieb:
The ports latest version of CUPS is 1.5.4; however version 1.7.0 has
been out since 10/24/13. Is there any possibility that the latest
version will make it into the ports system soon?
Careful with what you are asking for, have you checked the upstream
change logs? 1.6 already broke some aspects of compatibility
massively w.r.t. distributed printing or differing CUPS versions in
your LAN.
Well, almost any updated software has the potential to break something,
CUPS being no exception. However, those cases are not the norm and the
fact that in a few edge cases problems have been discovered is not a
sound reason for unilaterally failing to include the new version in the
posts system. There have been numerous cases where a new version of a
port was introduced into the system. In many of those cases workarounds
were introduced to allow the user to continue with the older version or
update to the newer one. I fail to see why that would not be acceptable
in this instance. In any case, how do you propose to find problems with
a new product if it is not tested in a real environment? In a worse
case scenario, a new port, perhaps cups-devel could be created.
--
Jerry
{Please don't CC me. I am on the list.}
___
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
I meant deliberate changes in concepts, not just happenstances... Check what
Fedora and other Linux distros have been doing to work around those before you
complain.
And remember this is a volunteer project, you are not paying to get upgrades
within the week...
___
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: Updating CUPS
On Thu, 26 Dec 2013 18:30:07 +0100, Matthias Andree stated: I meant deliberate changes in concepts, not just happenstances... Check what Fedora and other Linux distros have been doing to work around those before you complain. And remember this is a volunteer project, you are not paying to get upgrades within the week... I have done some checking on what is transpiring with CUPS on other distros. Actually, what happens there is not truly germane to FreeBSD though. In all too many instances, software that works perfectly fine there does not exhibit the same degree of suitability under FreeBSD architecture. Furthermore, version 1.5.4 (the ports version) was released on 7/25/12. The senior release version of the 1.6 family, 1.6.3 was released on 7/11/13. The 1.7 family was introduced shortly afterwards. Apparently, FreeBSD has skipped the entire 1.6.x branch. All I asked was if an updated version of CUPS was planned to be introduced into the ports system. I never said I was paying to get updates; although I have on several occasions voiced my opinion, along with others, that hiring professionals to maintain some ports or other areas of FreeBSD that seem to either get neglected or lag behind other operating systems might be a good investment. In any case, you obviously have no personal knowledge of what is transpiring with this port so further discussions with you are futile. -- Jerry ___ 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: Updating CUPS
26.12.2013 22:29, Jerry пишет: All I asked was if an updated version of CUPS was planned to be introduced into the ports system. I run 1.7.0 at my system for two weeks. However there are some problems I'm working on. Sorry, no time estimation for now. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: Updating CUPS
On Thu, Dec 26, 2013 at 11:03:48PM +0400, Boris Samorodov wrote: 26.12.2013 22:29, Jerry пишет: All I asked was if an updated version of CUPS was planned to be introduced into the ports system. I run 1.7.0 at my system for two weeks. However there are some problems I'm working on. Sorry, no time estimation for now. Thanks for working on this! Bapt pgpZWzMaggJ1n.pgp Description: PGP signature
Re: Updating CUPS
Jerry je...@seibercom.net schrieb: The ports latest version of CUPS is 1.5.4; however version 1.7.0 has been out since 10/24/13. Is there any possibility that the latest version will make it into the ports system soon? Thanks! -- Jerry ___ 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 Careful with what you are asking for, have you checked the upstream change logs? 1.6 already broke some aspects of compatibility massively w.r.t. distributed printing or differing CUPS versions in your LAN. ___ 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
