Rodrigo Barbosa wrote:
On Tue, Apr 17, 2007 at 05:17:00PM -0700, centos@911networks.com wrote:
When I am looking for a package that does not exist under rhel5, is it better to get rhel4 or fc6?
Get RHEL5 and install the fc6 package on it.
Or better yet, grab the FC6 SRPM and recompile it on your RHEL5/FC6 to be sure all your shared libraries, etc match. Very simple to setup and perform as a non-root user:
#configure your non-root user's rpm build environment
mkdir $HOME/rpm mkdir $HOME/rpm/SOURCES mkdir $HOME/rpm/SPECS mkdir $HOME/rpm/BUILD mkdir $HOME/rpm/SRPMS mkdir $HOME/rpm/RPMS mkdir $HOME/rpm/RPMS/i386 echo "%_topdir $HOME/rpm" >> $HOME/.rpmmacros
#build the rpm against your installed platform
rpmbuild --rebuild your-fc6.src.rpm
Jay
Jay Lee wrote: [snip]
Or better yet, grab the FC6 SRPM and recompile it on your RHEL5/FC6 to be sure all your shared libraries, etc match. Very simple to setup and perform as a non-root user:
#configure your non-root user's rpm build environment
mkdir $HOME/rpm mkdir $HOME/rpm/SOURCES mkdir $HOME/rpm/SPECS mkdir $HOME/rpm/BUILD mkdir $HOME/rpm/SRPMS mkdir $HOME/rpm/RPMS mkdir $HOME/rpm/RPMS/i386 echo "%_topdir $HOME/rpm" >> $HOME/.rpmmacros
#build the rpm against your installed platform
rpmbuild --rebuild your-fc6.src.rpm
Then once the rpm has been built, cd to $HOME/rpm/RPMS/i386 [or $HOME/rpm/x86_64 as the case may be], and do (as root):
# yum localinstall $HOME/rpm/i386/your_just_built_package.rpm [or x86_64 as appropriate to your environment]
On Tue, 2007-04-17 at 20:14 -0600, Peter Gross wrote: ...
Then once the rpm has been built, cd to $HOME/rpm/RPMS/i386 [or $HOME/rpm/x86_64 as the case may be], and do (as root):
# yum localinstall $HOME/rpm/i386/your_just_built_package.rpm [or x86_64 as appropriate to your environment]
If you do this often, or for multiple machines, you may want to have a look at
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
On 4/18/07, Phil Schaffner Philip.R.Schaffner@nasa.gov wrote:
On Tue, 2007-04-17 at 20:14 -0600, Peter Gross wrote:
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
A couple of questions or comments about number 4. How would you add the comps.xml group support (createrepo line)? I run my script as me, not root, and my umask is 027. So, in my case, I need to do a 'chmod -R o+rX' to make them readable by others. This format may be more general than the 'o-w+r' .
Akemi
On Wed, Apr 18, 2007 at 11:52:56AM -0700, Akemi Yagi wrote:
On 4/18/07, Phil Schaffner Philip.R.Schaffner@nasa.gov wrote:
On Tue, 2007-04-17 at 20:14 -0600, Peter Gross wrote:
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
A couple of questions or comments about number 4. How would you add the comps.xml group support (createrepo line)?
What I did for Fedora Core 6, that should work for Centos: 1. copy comps.xml from dvd_iso/repodata to local/repodata/comps.xml 2. copy <data type="group"> node from dvd_iso/repodata/repomd.xml to local/repodata/repomd.xml, and fix <location> node to point to local repodata/comps.xml: <data type="group"> <location xml:base="media://1161131669.029329#1" href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data> became: <data type="group"> <location href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data>
On 4/18/07, Luciano Miguel Ferreira Rocha strange@nsk.no-ip.org wrote:
On Wed, Apr 18, 2007 at 11:52:56AM -0700, Akemi Yagi wrote:
On 4/18/07, Phil Schaffner Philip.R.Schaffner@nasa.gov wrote:
On Tue, 2007-04-17 at 20:14 -0600, Peter Gross wrote:
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
A couple of questions or comments about number 4. How would you add the comps.xml group support (createrepo line)?
What I did for Fedora Core 6, that should work for Centos:
- copy comps.xml from dvd_iso/repodata to local/repodata/comps.xml
- copy <data type="group"> node from dvd_iso/repodata/repomd.xml to local/repodata/repomd.xml, and fix <location> node to point to local repodata/comps.xml:
<data type="group"> <location xml:base="media://1161131669.029329#1" href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data> became: <data type="group"> <location href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data>
Once the comps.xml file has been copied, can't you just run:
createrepo -g /path/to/comps.xml
Or is the manual editing required?
Akemi
On Wed, Apr 18, 2007 at 12:18:27PM -0700, Akemi Yagi wrote:
Once the comps.xml file has been copied, can't you just run:
createrepo -g /path/to/comps.xml
Or is the manual editing required?
createrepo -g should be enough, I did the manual edit because I already had the repodata created and this was faster than recreating it. :)
On Wed, 2007-04-18 at 12:18 -0700, Akemi Yagi wrote:
On 4/18/07, Luciano Miguel Ferreira Rocha strange@nsk.no-ip.org wrote:
On Wed, Apr 18, 2007 at 11:52:56AM -0700, Akemi Yagi wrote:
On 4/18/07, Phil Schaffner Philip.R.Schaffner@nasa.gov wrote:
On Tue, 2007-04-17 at 20:14 -0600, Peter Gross wrote:
http://wiki.centos.org/HowTos/CreateLocalRepos
Phil
A couple of questions or comments about number 4. How would you add the comps.xml group support (createrepo line)?
What I did for Fedora Core 6, that should work for Centos:
- copy comps.xml from dvd_iso/repodata to local/repodata/comps.xml
- copy <data type="group"> node from dvd_iso/repodata/repomd.xml to local/repodata/repomd.xml, and fix <location> node to point to local repodata/comps.xml:
<data type="group"> <location xml:base="media://1161131669.029329#1" href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data> became: <data type="group"> <location href="repodata/comps.xml"/> <checksum type="sha">dd46eef8b000e1b23430dace28c86061cf98ae74</checksum> <timestamp>1160767285</timestamp> </data>
Once the comps.xml file has been copied, can't you just run:
createrepo -g /path/to/comps.xml
Or is the manual editing required?
wrt editing comps.xml ... it depends.
If you are adding new packages that do not currently exist and want to get them to show up in an existing group, you will need to add them to that group ...
If you want to add a new group, and put packages in there, then you would do that.
If you are happy with the groups and package selections as they are ... then use current one.
Thanks, Johnny Hughes
On 4/20/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Wed, 2007-04-18 at 12:18 -0700, Akemi Yagi wrote:
Or is the manual editing required?
wrt editing comps.xml ... it depends.
If you are adding new packages that do not currently exist and want to get them to show up in an existing group, you will need to add them to that group ...
If you want to add a new group, and put packages in there, then you would do that.
If you are happy with the groups and package selections as they are ... then use current one.
I am only slowly understanding this...
In other words, IF comps.xml was edited, THEN running createrepo -g comps.xml makes sense ? Otherwise createrepo would not create anything new. It will just re-create the repodata files. Did I put it correctly?
Akemi
On Fri, 2007-04-20 at 19:11 -0700, Akemi Yagi wrote:
On 4/20/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Wed, 2007-04-18 at 12:18 -0700, Akemi Yagi wrote:
Or is the manual editing required?
wrt editing comps.xml ... it depends.
If you are adding new packages that do not currently exist and want to get them to show up in an existing group, you will need to add them to that group ...
If you want to add a new group, and put packages in there, then you would do that.
If you are happy with the groups and package selections as they are ... then use current one.
I am only slowly understanding this...
In other words, IF comps.xml was edited, THEN running createrepo -g comps.xml makes sense ? Otherwise createrepo would not create anything new. It will just re-create the repodata files. Did I put it correctly?
comps.xml is the file that provides the GROUP functionality for the yum repodata files.
So, if you add any packages, then you want to rerun createrepo (and use the -g comps.xml option).
If you are only adding updates to current packages and not adding any ADDITIONAL packages, using the current comps.xml file is fine.
If you are adding additional packages and not just updates to current packages ... AND IF you want them to show up in the selection menus for either a "yum groupinstall" ... OR IF you want them to show up as installable via anaconda ... OR IF you want them to show up in yumex or pirut (system-install-packages) in the "Group" areas then you will need to add any new GROUPS and/or PACKAGES into comps.xml.
If you add additional packages to the repo and do not add them to comps.xml, then they will not be selectable via an anaconda install or via "yum groupinstall". They will be available under yumex and purit ... but not in any groups.
Hopefully this explains the functionality of comps.xml
On 4/21/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Fri, 2007-04-20 at 19:11 -0700, Akemi Yagi wrote:
In other words, IF comps.xml was edited, THEN running createrepo -g comps.xml makes sense ? Otherwise createrepo would not create anything new. It will just re-create the repodata files. Did I put it correctly?
comps.xml is the file that provides the GROUP functionality for the yum repodata files.
So, if you add any packages, then you want to rerun createrepo (and use the -g comps.xml option).
If you are only adding updates to current packages and not adding any ADDITIONAL packages, using the current comps.xml file is fine.
If you are adding additional packages and not just updates to current packages ... AND IF you want them to show up in the selection menus for either a "yum groupinstall" ... OR IF you want them to show up as installable via anaconda ... OR IF you want them to show up in yumex or pirut (system-install-packages) in the "Group" areas then you will need to add any new GROUPS and/or PACKAGES into comps.xml.
If you add additional packages to the repo and do not add them to comps.xml, then they will not be selectable via an anaconda install or via "yum groupinstall". They will be available under yumex and purit ... but not in any groups.
Hopefully this explains the functionality of comps.xml
Better than any documentation available on earth. :) Thanks!
Akemi
-
Akemi Yagi -
Jay Lee -
Johnny Hughes -
Luciano Miguel Ferreira Rocha -
Peter Gross -
Phil Schaffner