Near the end of the install, a panel lists dozens of patches, some categorized as “Security”, others as “Recommended”, each preceded by a checkbox. I started to check all of the patches, but then noticed that the checks were bringing in software I had not requested – e.g., checking an emacs patch brought in emacs. Rather than bring in all of this additional software, I left all patches unchecked. Now I need to know how I can go back and apply only the patches that pertain to software that I have actually installed.
I’d also like to know whether there is some way to limit the install program panel to relevant patches only.
It’s important to realise that if a package requires other packages these other packages must be installed also, (this assumes you want a reliable system).
Now I need to know how I can go back and apply only the patches that pertain to software that I have actually installed.
Use YaST control center-online update, allow only the updates you want, If you are new to openSUSE you should ask more about setting up repo’s etc.Please check the info here New User How To/FAQ (read only)
On 2010-10-02 08:36, Iconoclasmic wrote:
>
> Near the end of the install, a panel lists dozens of patches, some
> categorized as “Security”, others as “Recommended”, each preceded by a
> checkbox. I started to check all of the patches, but then noticed that
> the checks were bringing in software I had not requested – e.g.,
> checking an emacs patch brought in emacs. Rather than bring in all of
> this additional software, I left all patches unchecked. Now I need to
> know how I can go back and apply only the patches that pertain to
> software that I have actually installed.
>
> I’d also like to know whether there is some way to limit the install
> program panel to relevant patches only.
First, I never allow to install updates or patches during the initial installation. I prefer to
finish the installation, and when the install is finished and the system works, then I run YOU to
apply patches.
There may be exceptions, of course. Like when it is known that a certain machine will not boot after
install due to a bug corrected later.
Second, you do not need to mark/unmark any patches, it is automatic. Just let yast choose the
patches, and only modify it if you know better.
Third, as I assume you are new to suse, don’t start by adding new repositories. At least till the
system is running, and you really know you need some thing.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
The information about repositories does raise one question for me: How does the new technology relate to RPM’s? I’d like to install Opera 10.62, for example. Can I just download the RPM from the Opera site and use RPM -i? Is that perfectly safe? How would I install Opera if I were going through the repositories, using YAST or Zypper?
Second, you do not need to mark/unmark any patches, it is automatic.
In that case, why does the install program even show the panel?
The install program is a beautiful piece of software. In most cases the options are clear and well-documented. But there are a few areas where documentation is missing and things are unclear. For example, what do the different kinds of checkmarks signify in the software selection panel? And why the patch selection panel?
> The information about repositories does raise one question for me: How
> does the new technology relate to RPM’s?
Repositories keep RPMs prepared for installation.
> I’d like to install Opera
> 10.62, for example. Can I just download the RPM from the Opera site and
> use RPM -i?
Yes, you could.
> Is that perfectly safe?
I don’t know about opera, but I suppose it is.
> How would I install Opera if I
> were going through the repositories, using YAST or Zypper?
You’d search for any repo keeping opera. I have found 10.61 for the distro I use, 11.2.
>> Second, you do not need to mark/unmark any patches, it is automatic.
>
> In that case, why does the install program even show the panel?
In case you want to.
> The install program is a beautiful piece of software. In most cases
> the options are clear and well-documented. But there are a few areas
> where documentation is missing and things are unclear. For example,
> what do the different kinds of checkmarks signify in the software
> selection panel?
I think the help panel explains it. Or clicking to change one.
> And why the patch selection panel?
You may want/need it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
My fear is that YAST and zypper maintain files that will not be updated if I bypass them and go directly to the RPM. How will YAST know that I have installed opera, if I use the RPM command?
Could I make the opera download site a temporary repository? Sorry if these questions seem foolish: I’m just trying to get a clear understanding of the process.
Well as far as I know, Yast doesn’t know if you install your software directly from the rpms.
This happens to me all the time since I’m pretty quick to install new versions of firefox faster than the updates supplied by Suse. I DO take care to install that in the same diretory as the original firefox, though, so when the updater gets around to it, I get the new version by the installer…
On 2010-10-03 10:06, Iconoclasmic wrote:
>
> Thanks again for the answer, Carlos E. R…
>
> My fear is that YAST and zypper maintain files that will not be updated
> if I bypass them and go directly to the RPM. How will YAST know that I
> have installed opera, if I use the RPM command?
Yast knows - it knows about any rpm you install by whatever means proper for rpms.
Yast does use the command “rpm” to do the actual installation. And that command maintains a database
of everything installed, which yast also queries (directly or via rpm, I do not know).
What may happen, though, is that yast may want to update packages installed externally, when it
finds a newer version.
> Could I make the opera download site a temporary repository?
Only if they have the metadata that makes a site (or directory) a repository. Which I assume they don’t.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
