EPEL/FAQ - Fedora. Project What is EPEL? EPEL (Extra Packages for Enterprise Linux) is a volunteer- based community effort from the Fedora project to create a repository of high- quality add- on packages that complement the Fedora- based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, such as Cent. OS and Scientific Linux. As part of the Fedora packaging community, EPEL packages are 1. FLOSS). A large number of contributors and users of Fedora and Enterprise Linux want to work within Fedora to provide these packages. The Fedora Project is a user of EPEL packages within the Fedora infrastructure itself. The Fedora Project is in a position to know the pain of not having a desired piece of software included in the RHEL distribution, and also a unique position to do something about it. Although RHEL is derived from Fedora, only a commercially supported subset of Fedora derived packages are included in the RHEL distribution. By sponsoring the EPEL project, Fedora contributors and users gain in many ways. Is EPEL commercially supported by Red Hat? ![]() Version: RHEL-6.9 Rating: 5 Date: 2017-09-04 Votes: 0: Although Red Hat's commitment to providing long-term security support for packages is extremely commendable. Introduction. Koozali SME Server is a complete, secure, stable and versatile Open Source Linux Server distribution for small to medium sized enterprises. # RPMパッケージのアップデート sudo yum upgrade # RPMパッケージのインストール sudo yum install kernel-devel gcc. No. EPEL is a volunteer effort from the Fedora community. Just like Fedora itself, Red Hat hosts infrastructure for this project and Red Hat engineers are involved as maintainers and leaders but there are no commercial support contracts or service level agreements provided by Red Hat for packages in EPEL. Which releases of Red Hat Enterprise Linux or derivatives does EPEL project provides packages for? EPEL project provides add- on packages for Red Hat Enterprise Linux 7, 6, and 5 releases and compatible derivatives (e. Cent. OS). Packages for Red Hat Enterprise Linux 4, 3 and 2 are not provided because these releases are at End of Life per Red Hat's errata support policy. Also, over time, Fedora diverges from older RHEL releases, and it can become more difficult to maintain packages that must build against against the older RHEL versions. How is EPEL different from other third party repositories for RHEL and derivatives? EPEL packages are in most cases built or derived from the equivalent ones in Fedora repository and maintained by the same people. It has also been improved through peer reviews, testing and feedback from end users. EPEL adheres to the well documented Fedora Packaging guidelines , which RHEL has started following. This ensures good integration. EPEL is purely a complementary add- on repository and does not replace packages in RHEL or layered products. EPEL has a large team of contributors including Red Hat engineers and volunteer community members working together to maintain the repository. EPEL only provides free and open source software unencumbered by patents or any legal issues. See also Cent. OS FAQ on alternate repositories. Are EPEL packages available only for RHEL or also for compatible derivatives? Packages are freely available and it is an explicit goal of the project to make sure they are usable for RHEL- based distributions such as Cent. OS and Scientific Linux. ![]() Does EPEL replace packages provided within Red Hat Enterprise Linux or layered products? No. EPEL is purely a complementary repository that provide add- on packages. EPEL will not conflict with any of the channels/layered products that it builds against. That is currently. For EPEL5 and EPEL6. EPEL will coordinate with other channels/products to minimize any conflicts, but may replace or cause issues with other channels. What is the policy on updates for packages in EPEL? Refer to the EPEL package maintenance and updates policy for all the details. How does Fedora Project ensure the quality of the packages in EPEL? Packages are peer reviewed against extensive packaging guidelines before being imported into the repository. Only updates that fix important bugs get pushed to the stable repository directly. Other updates hit a testing repository first and get released as an EPEL scheduled update in parallel with the EL scheduled updates. Packages often are tested in Fedora, too. Monitorix - A free open source lightweight system monitoring tool for Linux/UNIX servers and embedded devices.![]() The Fedora Packaging Guidelines and QA team back up all these efforts, helping to avoid errors. There are also discussions for more strict QA policies. Do participate and help us. How long are EPEL packages updated? The plan is for EPEL packages to get updates as long as the corresponding RHEL release is supported. That is 1. 0 years after the initial release according to the current errata support policy for 5, 6, and 7 releases. How can we be sure that someone will maintain the packages until end of life of the distribution the packages were built for? The only way to be sure is to do it yourself, which is coincidentally the reason EPEL was started in the first place. Software packages in EPEL are maintained on a voluntary basis. If you to want ensure that the packages you want remain available, get involved directly in the EPEL effort. More experienced maintainers help review your packages and you learn about packaging. If you can, get your packaging role included as part of your job description; EPEL has written a generic description that you can use as the basis for adding to a job description. We do our best to make this a healthy project with many contributors who take care of the packages in the repository, and the repository as a whole, for all releases until RHEL closes support for the distribution version the packages were built for. That is ten years after release (currently) - - a long time frame, and we know a lot can happen in ten years. Your participation is vital for the success of this project. What if my ISV/IHV wants to maintain a package in EPEL? Software and hardware vendors are encouraged to get involved in EPEL. For more information, read the ISV/IHV Perspective. Why isn't a package in EPEL- 7 when it is in EPEL- 6? Packages are not automatically branched for each EPEL version. Each package must be branched by a packager for each particular release, and packagers may or may not be interested in EPEL- 7 while they were interested in EPEL- 6. If you are an EPEL- 7 user and you want an EPEL- 7 branch, it's a good idea to ask the existing EPEL or Fedora maintainer. This lets the current maintainer know that there are real users who would benefit from the package (instead of simply guessing at the size of the user base). The preferred method of asking a maintainer for an EPEL- 7 branch is to file a ticket in bugzilla against the "el. If there is no el. Rawhide version instead. If you want to check the current ownership of a package (perhaps to contact the owner directly), you can search pkgdb. You can also use zodbot on IRC to query pkgdb on your behalf. User: jjh, Name: None, email: jeremy@hinegardner. Creation: 2. 00. 7- 0. IRC Nick: None, Timezone: None, Locale: None, GPG key ID: None, Status: active. Approved Groups: cla_fedora cla_done fedorabugs packager cla_fpca. For more information, see the Getting a Fedora package in EPEL page. Using EPEL How can I install the packages from the EPEL software repository? There are repository rpm packages for RHEL5, RHEL6 and RHEL7. The repository package installs the repo. Then you can install packages with your usual method, and the EPEL. Uvh http: //download. Uvh http: //download. Uvh http: //download. Where is the software repository located? EPEL packages are located at master mirror . There are mirrors available at mirror list . Where can I find help or report issues? You can find help or discuss issues on the epel- devel mailing list or IRC channel #epel on Freenode. Report issues against EPEL via bugzilla. How do I know that a package is a EPEL package? All EPEL packages are signed with the EPEL gpg- key. The public key with id 2. F6 is part of the epel- release package for epel 5; The public key with id 0. B8. 95 is part of the epel- release package for epel 6; yum will ask you to import it the first time you install a EPEL package. See also. https: //fedoraproject. EPEL is just one of several add on repositories with RPM packages for RHEL and derivates. It is not an official repository. The different repositories serve different user bases or follow different ideas. Just like RHEL itself, EPEL in reality is more a "downstream" in the sense that Fedora is upstream and EPEL, just like Red Hat, takes packages for its product that are constantly developed, tested and receive feedback in Fedora. Red Hat, through their sponsorship for the Fedora project and participation of Red Hat maintainers, continues to back EPEL, but Red Hat has not endorsed EPEL or commercially supported it. Building From Source on Linux — Sci. Py. org. ATLAS is a BLAS/LAPACK implementation which tuned itself on the machine to provide ideal performances, and often match vendor specific implementations. Unfortunately, building ATLAS is not easy. But, it is getting easier all the time. These instructions show how to build ATLAS (and LAPACK) from their official distributions. First, download and unpackage the LAPACK distribution from netlib (you need these to build a complete version of LAPACK). There are several make. INSTALL directory of the lapack distribution. Copy one of those files to the main directory. For example: cp. INSTALL/make. Now, you must edit the make. OPTS and NOOPT lines both contain the flag for compiling position- independent code on your platform (e. PIC). For example: OPTS=- O2- f. PICNOOPT=- O0- f. PIC(Note: Make sure that if you build with gfortran that g. PATH when numpy is being built) as you need to link with the same compiler that you built lapack with when numpy builds. It will try and find g. Then change to the SRC directory and run make. This will create an lapack_< XXXX>. You will need the location of this file to configure atlas. Now, download the latest release of ATLAS (these instructions worked on 3. See, for example, https: //sourceforge. Unpackage the result, change to the directory created, and create a directory to contain the resulting build. This directory should be named appropriate for the platform (you can build for multiple platforms from the same SOURCE tree — perhaps the source is on a network drive and builds are taking place for multiple platforms). ATLASmkdir. ATLAS_< my_platform_type> cd. ATLAS_< my_platform_type>./configure- Faalg- f. PIC- -with- netlib- lapack=/path/to/lapack/lapack_< XXXX>. Your atlas libraries should now be in the lib subdirectory of the current directory. You should copy them to some- place that you can tell site. If you want to create shared libraries, then you can do that bycdlibmakeshared# for sequential librariesmakeptshared# for threaded librariesafter changing to the lib directory where the . ATLAS almost painless: it will build a complete LAPACK, build it with the right fortran compiler to avoid ABI issues (eg _gfortran_string_write, etc..), and with the right compiler flags such as it is usable to build numpy and scipy (with the - f. PIC option). First, download the source rpm included in the ashigabou repository (the file atlas- version. Then, use the following: rpm- ivhatlas- version. This will NOT install atlas, just uncompress all the necessary files for building the rpm in /usr/src/packages. Before building atlas, you must disable dynamic change of CPU frequency (used to decrease battery consumption): cpufreq- selector- gperformance. If this fails telling you no cpufreq support, this is fine. Now, to build the rpm, go into the directory /usr/src/packages/SPEC, and execute. This will build the rpm: this can take a long time, even on a powerful machine. What matters is whether atlas has arch defaults for your machine: if not, it can take several hours (it takes 2 hours and a half on a P4 @3. Ghz, but takes ~1. If successfull, you will get an installable rpm in /usr/src/packages/RPMS/ARCH (where ARCH can be x. The rpm contains two (shared) libraries: libblas. They are meant to be drop- out for the standard BLAS and LAPACK (the ones in refblas. To use the atlas libraries, once you installed numpy and scipy, you should tell the OS to use atlas instead of default libraries by using LD_LIBRARY_PATH. That is, normally, you can use numpy by : python- c"import numpy as N; a=N. N. dot(a, a)"To use atlas, you do: LD_LIBRARY_PATH=/usr/lib/atlas/sse. N; a=N. random. randn(1. N. dot(a, a)"If everything is working correctly, you will see that the above script runs much faster with atlas than without (I see a ten fold speed increase on my machine).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |