[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

policy manual suggestion



Hi,

sorry for not making suggestments how to word the changes, but i consider my
englis as too bad to try :)

#2.1 Main Distribution Section
#
#   All packages in the Debian distribution proper must be freely useable,
#   modifiable and redistributable in both source and binary form.[1] It
#   must be possible for anyone to distribute and use modified source code
#   and their own compiled binaries, at least when they do so as part of a
#   Debian distribution.
#
#[1]
#   It is OK for there to be a requirement that modified versions carry a
#   warning, or that they be released with a different name or version
#   number, or something similar, because we can comply with this
#   requirement if necessary.

Perhaps we should add something about lib licenses? Especially that
development toolkits in the main section are not allowed to place any policy
on the compiled program. Especially that the lib has to be under LGPL
instead of GPL? Otherwise developing on a "Main Section" Debian System _can_
be unable for commercial Applications.

# 2.2 non-free Section

Can we require the copyright files of all non-free packages have to mention
why a package is in non-free, in 2.2 and 3.2.6.

# 3.2 location if files

The default place for the FHS (FSSTND) Project is
http://www.pathname.com/fhs/ It will use the name FHS for the next standard,
dont know if we want to switch, yet?

# 3.2.1 Manpages
ln -s ../man7/undocumented.7 \
 debian/tmp/usr/man/man[1-9]/the_requested_manpage.[1-9]

shouldn't this be a symlink from .gz to .gz?

# 3.2.4 Preferred documentation formats

Add somthing like: if you provide html-docu for a package you should set up
a file /usr/doc/package/index.html, which is pointing to all available docu
of that package.

Add something like:

+3.2.10 generated Files
+
+It's recommended that you place all installed files of a package into the
+binary archive on their final location, unless it is neccessary to
+move/generate the files in postinst script. Don't move files around without
+a real reason (conditional configuration or conflicts).

3.6
#   Shell scripts (sh and bash) should almost certainly start with set -e
#   so that errors are detected. Every script must use set -e or check the
#   exit status of every command.

I would suggest that rm-scripts should not use -e, since it is anoying if
you can't update a package, only because the /etc/init.d/package file was
deleted and the scripts are unable to run them. (unfortunatelly one has to
remove or move the init.d scripts to run "update-rc.d remove" (why?))

Greetings
Bernd







--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com


Reply to: