So I have to tell it to keep all the RPMs so it will keep the source files? But what I want it to do is to *install* the source file rpm so I can read the source files. That's what I assumed would happen when running rpm -i against the src rpm. In fact, I thought that the source files would end up in /usr/src somewhere such as /usr/src/redhat/SRPM. But I don't see that happening. I have some source rpms and I have installed them but the rpm database doesn't show they are installed, just the package that they (should) build. If I install 'foo.rpm', then 'rpm -qa | grep foo' will return 'foo'. If I install 'foo.src.rpm' then 'rpm -qa | grep foo' will also show 'foo', not 'foo' and 'foo.src' as I expect. My view of SRPMs comes from (over)generalizing the development packages: if I install 'foo.develop.rpm' and 'foo.rpm', 'rpm -qa | grep foo' will return 'foo' and 'foo.develop'. So I guess I need to ask the purpose of an SRPM if not to install source files? How do I get source files on my system? Thanx all... Hattie Rouge > -----Original Message----- > From: psyche-list-admin@xxxxxxxxxx > [mailto:psyche-list-admin@xxxxxxxxxx] On Behalf Of Dale > Sent: Saturday, May 03, 2003 12:45 PM > To: psyche-list@xxxxxxxxxx > Subject: Re: using up2date for source as well as binaries > > > On Sat, May 03, 2003 at 11:52:37AM -0700, Hattie Rouge wrote: > > I want to have complete source and binary packages on one of my > > machines. What is the easiest way to do this? I assumed > that adding > > the --src flag to up2date would do this but I don't see that it has. > > > > Perhaps I am missing something here. I figured that a > > *86.src.rpm file was the source code for a matching rpm > file and when > > installed would leave source code files in /usr/src/redhat. > It doesn't > > seem to work that way. > > > > Should I be looking at checking out a source tree via CVS? > > No, CVS is not applicable for this case. > > up2date (by default, at least) stores retrieved rpms (both binary and > source) in /var/spool/up2date. The "Package storage > directory" field in up2date-config or "up2date --config" > allows you to change that. > > I'm under the impression that if you let up2date itself do > the install that unless you select the option to keep binary > packages (in up2date-config) up2date will delete the binary > packages after installation is done. I can't confirm that > statement from personal experience, as I use up2date for > download only and then do the installation myself. > > Directory /usr/src/redhat is not generally used as a storage > place for RPM packages. I'd advise storing them some place else. > > > I figured that a > > *86.src.rpm file was the source code for a matching rpm > file and when > > Not precisely. The binary rpm files are generally named in a > way similar to the .src.rpm, but a single .src.rpm often > results in multiple binary packages with different names. > The "*86" part of the binary package file name describes the > target for which the package was built (e.g., i386, i686, > i586, noarch, athlon). > > An example of package naming: > > Binary packages > vte-0.10.25-1.i386.rpm > vte-devel-0.10.25-1.i386.rpm > come from source rpm > vte-0.10.25-1.src.rpm > > > > -- > Psyche-list mailing list > Psyche-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/ps> yche-list > -- Psyche-list mailing list Psyche-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/psyche-list
