[Bug 230986] www/linux-flashplayer: Separate c6 and c7?

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230986

--- Comment #10 from Jason W. Bacon <jwb at freebsd.org> ---

CentOS 6 is nearing EOL and support from vendors is already waning.  We need to
make c7 practical for average users to manage before that happens, so it can be
well tested before becoming the default.

I don't much care what the solution looks like, but I think it's important that
people can choose freely between c6 and c7, and safely run a pkg upgrade in
either case.

I'll explore using flavors instead of separate ports.  The only major
shortcoming with c7 is the lack of binary packages for flashplayer and
comparable ports, so any solution that gets both c6 and c7 variants of the
packages into the repo would be satisfactory from my perspective.

I think it would be ideal if the system tried to build c6 and c7 flavors by
default (unless otherwise specified), as it does with python 2 & 3.  I suspect
some people will want to stick with c6 for some time after EOL for their own
valid reasons, so it will be important for both c6 and c7 to be well supported
for a while.

Many of us need to move onto c7 in the near future, though.  We will not longer
be running any real CentOS 6 systems after 2018.

I'm beginning to test a variety of engineering apps from ANSYS, Biovia, etc.  I
know linux compatibility is not a high priority for most FreeBSD users, but
we're in a good position right now to polish it up and make FreeBSD a more
viable platform for running commercial apps. 64-bit support and c7 are working
pretty well now, and RHEL/CentOS 7 are still young.  Any investment we make in
improving the system now will have a lasting benefit for the next several
years.

-- 
You are receiving this mail because:
You are the assignee for the bug.