Posted by: Administrator
on July 23, 2004 08:33 PM
1. Using up2date with your repository
Although everyone seems to have forgotten this, the Fedora Core up2date now has backend support for yum repositories. What I find really useful about making my own repositories is to not only have a mirror of the distribution, but to mirror an update server as well. I use a nightly cron job to pull released updates from a mirror after they've performed their mirror routines. I also mirror FreshRPMS and other useful repositories (such as Fedora Legacy for my Red Hat Linux 9 systems).
By setting up my<nobr> <wbr></nobr><tt>/etc/sysconfig/rhn/sources</tt> file, my desktop RHN applet tells me when there are updates available in any of my local repos by flashing its red exclamation mark. Then either my wife or I can have them installed using the simple GUI interface (or I ssh from work and do them via terminal for more speed). I don't even have to use<nobr> <wbr></nobr><tt>/etc/yum.conf</tt> since the yum support in up2date is built-in.
up2date seems to have been criminally ignored by many intermediate Linux users because they don't realize that it is no longer inextricably linked with Red Hat Network. Red Hat went to some trouble to build in yum and apt support so that Fedora Core would be more useful to the community. Don't be afraid to use it!
2. RPM release tag
Rather than setting the release tag from 1.1 to 1.2, a better idea would be to use 1.1.0.xxx, where xxx are your initials. That way, if an official release is tagged 1.2, it will override your custom 1.1.0.xxx RPM. If the officially released 1.2 has been changed to eliminate a bug or contains a security fix, you would want to rebuild the new RPM (which you would then tag 1.2.0.xxx).
Learn about Linux
Download Linux
Get Linux help
Two points...
Posted by: Administrator on July 23, 2004 08:33 PM1. Using up2date with your repository
Although everyone seems to have forgotten this, the Fedora Core up2date now has backend support for yum repositories. What I find really useful about making my own repositories is to not only have a mirror of the distribution, but to mirror an update server as well. I use a nightly cron job to pull released updates from a mirror after they've performed their mirror routines. I also mirror FreshRPMS and other useful repositories (such as Fedora Legacy for my Red Hat Linux 9 systems).
By setting up my<nobr> <wbr></nobr><tt>/etc/sysconfig/rhn/sources</tt> file, my desktop RHN applet tells me when there are updates available in any of my local repos by flashing its red exclamation mark. Then either my wife or I can have them installed using the simple GUI interface (or I ssh from work and do them via terminal for more speed). I don't even have to use<nobr> <wbr></nobr><tt>/etc/yum.conf</tt> since the yum support in up2date is built-in.
up2date seems to have been criminally ignored by many intermediate Linux users because they don't realize that it is no longer inextricably linked with Red Hat Network. Red Hat went to some trouble to build in yum and apt support so that Fedora Core would be more useful to the community. Don't be afraid to use it!
2. RPM release tag
Rather than setting the release tag from 1.1 to 1.2, a better idea would be to use 1.1.0.xxx, where xxx are your initials. That way, if an official release is tagged 1.2, it will override your custom 1.1.0.xxx RPM. If the officially released 1.2 has been changed to eliminate a bug or contains a security fix, you would want to rebuild the new RPM (which you would then tag 1.2.0.xxx).
#