On 02/04/14 11:16, Bennett Haselton wrote: > I understand (I think), but is it easy to tell me, or is there a > *reliable*, *vetted* source, describing for intermediate users how to > actually do this? i.e.: > 1) When you say "Try just core and EPEL packages to start with", are you > talking about which .repo files I should keep in my /etc/yum.repos.d > directory? OK, then which ones should be in there? Only the CentOS-* > ones that were in there by default? And *not* the rpmforge.repo one? > Does one of the default .repo files also include the EPEL packages? This depends if you already have dependencies on rpmforge. If you don't need them, remove that repo and just use the CentOS and EPEL repos for now. You may have a task here to really tidy up and remove all the fedora and rpmforge stuff. You can also make exceptions in the repo configs and the main repo config files to exclude sets of packages from those foreign repos. For example: exclude=perl* Check the man pages/documentation for more examples. > 2) And then if I want to install a module like Crypt::Twofish which > isn't included in the default packages, by "compiling a new package > based on the installed core and EPEL packages", then I do -- what? You will have to research package building a bit more yourself. http://wiki.centos.org/HowTos/SetupRpmBuildEnvironment You can also draw from examples of existing packages by getting their source RPMs and reading through the spec files. http://vault.centos.org/6.5/os/Source/SPackages/ > > I understand that if you already know the answers to these questions, it > seems like the answers are "obvious" or "easy to find on Google". The > problem is that's what got me here in the first place, because I did > look for answers from reliable sources on Google, and didn't know enough > to realize which parts of the directions were wrong. If I try to do the > next step based on directions from Google, I'm not doing to know when > the directions are misleading me there either. So I'm hoping someone > could tell me how to do it or could point me to directions that have > actually been vetted (meaning that someone showed the directions to at > least one intermediate-level user and said "Here, we want these > directions to be helpful to people, so try these out, let me know if you > get stuck, and we'll keep revising the directions until there are no > places where people get stuck any more."). Start with the above. You may have open a new thread for package building support.
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
