Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
On 11/23/2011 06:15 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
On 23/11/11 12:47, Johnny Hughes wrote:
On 11/23/2011 06:15 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
On 11/23/2011 09:48 AM, Ned Slider wrote:
On 23/11/11 12:47, Johnny Hughes wrote:
On 11/23/2011 06:15 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
We could do that if there is a need.
Putting this in the upstream bugzilla might get it turned on for the main distro.
On 11/23/2011 06:35 PM, Johnny Hughes wrote:
On 11/23/2011 09:48 AM, Ned Slider wrote:
On 23/11/11 12:47, Johnny Hughes wrote:
On 11/23/2011 06:15 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
We could do that if there is a need.
Putting this in the upstream bugzilla might get it turned on for the main distro.
Until then it's a perfect candidate for centosplus.
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
We could do that if there is a need.
Putting this in the upstream bugzilla might get it turned on for the main distro.
Ok, I am going to check if RHEL ships with Bytecode Interpreter already active. If not, I am going to create an upstream BZ.
Until then it's a perfect candidate for centosplus.
So centosplus may contain packages that are already in base? How is made sure that these are taken? By higher Release Tags or just by includes/excludes?
Greets Marcus
On 11/23/2011 11:37 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
We could do that if there is a need.
Putting this in the upstream bugzilla might get it turned on for the main distro.
Ok, I am going to check if RHEL ships with Bytecode Interpreter already active. If not, I am going to create an upstream BZ.
Until then it's a perfect candidate for centosplus.
So centosplus may contain packages that are already in base? How is made sure that these are taken? By higher Release Tags or just by includes/excludes?
We will add the .centos.plus "dist" tag, which will make it a higher than the other one for the same Name-Version-Release-Dist in the main repo.
On 11/23/2011 07:37 PM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
Wouldn't this be a candidate for the centosplus repo?
You build other packages with options different to upstream in centosplus (e.g, postfix with mysql support enabled)?
We could do that if there is a need.
Putting this in the upstream bugzilla might get it turned on for the main distro.
Ok, I am going to check if RHEL ships with Bytecode Interpreter already active. If not, I am going to create an upstream BZ.
Until then it's a perfect candidate for centosplus.
So centosplus may contain packages that are already in base?
Indeed.
How is made sure that these are taken? By higher Release Tags or just by includes/excludes?
by default centosplus is disabled. users must make sure that they include what's needed and exclude what is not. see http://wiki.centos.org/AdditionalResources/Repositories/CentOSPlus . In particular, ".centos" is also added to the release.
In my case, for instance: [base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... #baseurl=http://ftp.iasi.roedu.net/mirrors/centos.org/$releasever/os/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 exclude=postfix
#released updates [updates] name=CentOS-$releasever - Updates mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&rep... #baseurl=http://ftp.iasi.roedu.net/mirrors/centos.org/$releasever/updates/$basearch/ #baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 exclude=postfix
In this particular case , I have my own postfix ( mysql enabled, no pgsql) that I want to protect, but the idea is the same. In the initial days I used to use postfix-centos.mysql_pgsql.i386.rpm but I decided that the postgresql stack was useless for my use case and got rid of it.
Johnny Hughes wrote on 11/23/2011 07:47 AM:
On 11/23/2011 06:15 AM, Marcus Moeller wrote:
Hi all.
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
Greets Marcus
[1] http://www.freetype.org/patents.html _______________________________________________
Only if they build it that way in RHEL.
How about a RFE for centosplus?
Phil
On 11/23/2011 04:16 PM, Phil Schaffner wrote:
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
How about a RFE for centosplus?
Even better, open an issue report - and offer to maintain the package in centosplus !
- KB
On 11/24/2011 03:41 AM, Karanbir Singh wrote:
On 11/23/2011 04:16 PM, Phil Schaffner wrote:
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
How about a RFE for centosplus?
Even better, open an issue report - and offer to maintain the package in centosplus !
Let's assume I am willing to maintain it. For a package in fedora / EPEL I would do an equivalent of git push (push the package in fedora's GIT), koji build (build the package using fedora's builders ) and after that I'd push the package to the testing repo; sometime later the package would go to the stable repo or I'd be asked to fix "something" and I'd go thru the whole process again. Everything but the very final push step ( which requires signing ) is done with no need for human intervention ( but mine ) and is identical for all maintainers ( i.e. this is the regular flow)
What would be the exact procedure for centosplus ?
On 11/24/2011 04:12 PM, Manuel Wolfshant wrote:
Let's assume I am willing to maintain it. For a package in fedora / EPEL
...
What would be the exact procedure for centosplus ?
open an issue request at bugs.centos.org, include why you think it should be a part of the main centos.org repo's.
submit a srpm, find an existing centos developer / contributor to sponsor + audit it - once its in place, we setup a git repo with your key, setup a bugs.centos.org component with that name and your id as responsible for it, you can then request builds using an irc interface, which are pushed to the testing repo.
sign and move to release would need one of the key holders to verify and push accordingly. Btw, unless it is a component that overwrites a distro rpm, it can goto the contrib repo rather than the centosplus repo.
- KB
Karanbir Singh writes:
On 11/23/2011 04:16 PM, Phil Schaffner wrote:
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
How about a RFE for centosplus?
Even better, open an issue report - and offer to maintain the package in centosplus !
- KB
Sorry to pup-up so late but I'm very busy these days. I already have this freetype package for C6 in my personal repo, actually I've been using it for some days now without problems. http://li.nux.ro/download/nux/dextop/el6/SRPMS/freetype-freeworld-2.4.4-6.el...
(packages also available for i386 and x86_64)
It's a shameless rebuild from rpmfusion. I guess it could be a good starting point.
-- Nux! www.nux.ro
Hi again.
On 11/23/2011 04:16 PM, Phil Schaffner wrote:
As the patents for the Bytecode interpreter has been expired [1], I wonder if we could build freetype '--with bytecode_interpreter' set.
How about a RFE for centosplus?
Even better, open an issue report - and offer to maintain the package in centosplus !
- KB
Sorry to pup-up so late but I'm very busy these days. I already have this freetype package for C6 in my personal repo, actually I've been using it for some days now without problems. http://li.nux.ro/download/nux/dextop/el6/SRPMS/freetype-freeworld-2.4.4-6.el...
(packages also available for i386 and x86_64)
It's a shameless rebuild from rpmfusion. I guess it could be a good starting point.
To enable Bytecode Interpreter, you just have to rebuild the original (EL) freetype package with the '--with bytecode_interpreter' option set.
Greets Marcus
-
Johnny Hughes -
Karanbir Singh -
Manuel Wolfshant -
Marcus Moeller -
Ned Slider -
nux＠li.nux.ro -
Phil Schaffner