#LIBJANSSON CENTOS INSTALL#
(May also need to install and start NFS, and/or reboot if you have not been using it. Export the directory via NFS - if not already on a shared directory.Can be removed later if not required on server. Install packages on the server to test the repo.For HTTP or FTP repos the baseurl line must be changed accordingly.Name=CentOS-$releasever - local packages for $basearchīaseurl=file:///share/CentOS/$releasever/local/$basearch Another, arguably superior, alternative is to use PackageManagement/Yum/Priorities. It also assumes your packages are not GPG-signed. Warning: The example assumes yum-plugin-protectbase plugin (see PackageManagement/Yum/ProtectBase) is installed, and that you want your repo to be enabled by default, protected, and allowed to replace core packages.
home/builduser/rpmbuild/RPMS/foo-docs-1.2.3. home/builduser/rpmbuild/RPMS/foo-devel-1.2.3. ~]$ rpmbuild -rebuild /path/to/srpm/foo-1.2.3. This creates (for example) /home/builduser/rpmbuild/RPMS/foo-1.2.3. Build a spiffy new set of packages from foo-1.2.3. (or alternately get packages from another trusted source).If createrepo is not already installed, as it will not be by default, install it.First create directory structure on the server, say server1: ~]# mkdir -p /share/CentOS/4/local/i386/RPMS.Convention on command-line sections: # means run as root, $ means run as a user - builduser in the example. One can also use other means of providing access to the repo, such as a HTTPd and/or an FTP server. A similar approach can be followed for other architectures and versions. The example will cover i386 for CentOS4.avoiding downloading from external mirror servers, and controlling availability of updates to local machines until they have been tested. One can follow a similar procedure to enable local mirrors of os, updates, etc.
#LIBJANSSON CENTOS HOW TO#
The following procedure will explain how to set up an NFS share containing a repository of locally built/rebuilt/downloaded packages and access them in a uniform manner from other systems of the same distro version. Use of a yum repo adds additional benefits, as yum can resolve dependencies and automatically satisfy them from available repositories. One benefit of the rpm based approach, is that a developer can incrementally solve dependencies, and rpm will suggest what the next needed package must provide, and one can build up a 'just enough' solution: ~]# rpm -Uvh. Or the older and simpler approach for an unsigned package: ~]# rpm -Uvh Note: For a single package or a stand-alone end-user system, don't go through all the overhead of building a formal NFS export and package repository - just use either: ~]# yum -nogpgcheck localinstall If you have downloaded, created, or rebuilt RPM packages locally (as explained in TipsAndTricks/YumAndRPM "Get set up for rebuilding packages while not being root") you may want a place to put them so they are accessible from all the machines on your local net.
0 kommentar(er)
