On Mon, May 21, 2007 at 11:22:35PM +0300, Jabka Atu wrote:
> Howdy,..
God aften!
> i've started reading
> [URL="http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html"]this
> manual[/URL] to understand how to create better packages for debian so
> i have created a small package that i call
> [URL="http://downloads.sourceforge.net/scex/klthemes_1.0_all.deb?use_mirror=osdn"]klthemes[/URL]
> so here is the control file :
> [CODE]
> Source: klthemes
> Section: contrib
> Priority: extra
> Maintainer: Jabka Atu <mashrom.head@gmail.com>
>
> Package: klthemes
> Architecture: all
> Depends:
> Description: Collection of kdm themes collected from kde-look.org by
> Jabka Atu include the next themes: hardDrive, Debian Orange,
> Technodream, daemonic-smegma_1.0, devil, yellowrose,
> sidux-highway,optical scanning 2007, KdmLinux, Kubuntu KDM Gears
> (tux)[/CODE]
> Summary: collection of kdm themes
>
>
> all nice and good but i need little help :
>
> 1.from some reason instead of using one line for summary and more for
> description all went to summry.
The first line (i.e. the bit following "Description:") is the package
summary. This is a one-liner that dpkg, apt, aptitude and others will
display when showing package lists etc.
The more verbose description should be on *subsequent* lines, indented
by *one* space, i.e. like this:
Descripiton: Collection of kdm themes
Themes collected from kde-look.org by Jabka Atu include the next
themes: hardDrive, Debian Orange, Technodream, daemonic-smegma_1.0,
devil, yellowrose, sidux-highway,optical scanning 2007, KdmLinux,
Kubuntu KDM Gears (tux)[/CODE]
Note the indentation. Also note that the summary (the indented bit) will
not always be shown under the one-liner description: it has to make
sense on its own. All of this is available at:
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description
> 2.i need to add depends: kdetheme and some how to make it install it
> if it isn't allready installed:
> i understand that i need to use preinst script could you please
> provide an example for example if i have foo dependency how would my
> preinst will be ?
That is not the purpose of a preinst script. The package does not
concern itself with getting its dependencies installed (this is the job
of the package manage system). Instead you need to communicate your
dependency on them to the package management system.
What you need is a line like this:
Depends: kdetheme
For the full gory details, see
http://www.debian.org/doc/debian-policy/ch-relationships.html
Hope this helps
--
Karl E. Jorgensen
karl@jorgensen.org.uk http://www.jorgensen.org.uk/
karl@jorgensen.com http://karl.jorgensen.com
==== Today's fortune:
Talking about music is like dancing about architecture.
-- Laurie Anderson
Attachment:
signature.asc
Description: Digital signature