- The document doesn't gives overview of what is really a "package" in
Linux.
oh yes i noticed it too so started writing something , something on these
lines will it suffice ?
Index: package-installation.txt
===================================================================
--- package-installation.txt (revision 12)
+++ package-installation.txt (working copy)
@@ -2,7 +2,11 @@
Author - dhili...@gmail.com
+Software in the FOSS ( Free and Open source ) world comes in source form ,
which is the biggest strength and philosphy of this software developement
model , havig said that not every one is capable of recompiling the source
and make it work on there platforms. The are just intrested in executing
the software without the necessity of knowing what is going inside the
Software , pretty much like what you do on other operating systems like
Windows or Mac operating systems.
+A package is a precompiled bundle of source software to be installed on an
Operating system .
+
+
There are numerous package managers available for Linux systems. Several
of the package managers offer graphical front-ends, contain search
capabilities, allow updates to be installed from remote locations, and
provide E-mail notifications when new packages are available. One package
manager that provides all of these capabilities is YUM __(YellowDog Updater
Modified)__. This manual will provide an introduction to package management
with yum.
Here is something i wrote in the mean time,
== What is a package?
Package is prebuilt opensource component.
Package can be,
A collection of one or more programs that perform a single
well-defined task. This is normally what people think of as
an "application". Word processors and programming languages would fit into
this category.
A specific part of an operating system. Examples might be system
initialization scripts, a particular command shell, or the software
required to support a web server, for example.
In the beginning there was no package management, users have to compile
applications from source using GNU maketools.
This method is heavily discouraged as there is no concrete way to
remove/update/upgrade packages. You might leave behind files when you
intend to remove them.
The biggest advantage is that the package can contain the knowledge about
what it takes to install itself on your computer. And if the package
contains the steps required to install itself, the package can also contain
the steps required to uninstall itself. What used to be a painful manual
process is now a straightforward procedure. What used to be a mass of
20,000 files becomes a couple hundred packages.
A package manager keep tracks of the packages installed. It also keep
tracks of what is inside a package.
<taken from http://www.rpm.org/max-rpm/ >
You can also add something about: "Repositories"
Totally revised this manual, new revision at
https://code.google.com/p/foss-lab-manual/source/browse/trunk/lab-manual/package-installation/package-installation.txt?spec=svn32&r=32
Thanks for the contribution Arun. I have a few suggestions. There are
some common sequence of commands, that we usually come across. In the
foss-lab-manual we call them tasks. For the package installation lab,
I suggest that we have the following tasks.
1. Installing a package
Given a name of a software app, how do you search for a particular
pacakge,
install it. And finally how to list the files installed by the package.
2. Removing a package
List the packages installed to find out the name of the package. And
finally remove the package.
3. Updating a package
Check if updates are available, update the package. I guess this is
kind of tricky, since it is not easy to give a solid example(?)
> 1. Installing a package
> Given a name of a software app, how do you search for a particular pacakge,
> install it. And finally how to list the files installed by the package.
> 2. Removing a package
> List the packages installed to find out the name of the package. And
> finally remove the package.
Comment #9 on issue 9 by saga...@gmail.com: Installing various software
packages
http://code.google.com/p/foss-lab-manual/issues/detail?id=9
Changes in Revision 44:
http://code.google.com/p/foss-lab-manual/source/detail?r=44
- Moved the introduction about package management systems to
study-material/PackageManagentOverview.txt ( New file)
- Students are given with the task to install and remove bsd-games package
Changes in Revision 45:
http://code.google.com/p/foss-lab-manual/source/detail?r=45
- Installing VLC and removing it has been added as additional task for the
lab. It also involves configuring rpmfusion repositories.
Please review and provide your feedback. Thank you.