Re: Ark Linux packaging rules

Pupeno <[email protected]>
Newsgroups gmane.linux.arklinux.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 22 January 2004 13:01, Joan Sanfeliu wrote:
> It's me who was working on an RPM-HOWTO, i finally have corrected some
> issues and i'm attaching it here for you guys to review it, maybe we could
> join both documents into one?
No, I don't think so, becuase they have very specific diferent targets.
Your document is for people to learn how to make RPMs, everybody who doesn't 
know how to make RPM should read your document (even when not making RPMs for 
Ark) while my document is a set of rules for which every Ark RPM should 
apply, they're complementary documents, but diferent (your document should be 
explanatory, mine should be strict).
Now, what we should do is to be sure there aren't inconsistencies between 
documents and we should share the styles to make both of them look the same. 
We should even interlink between them, like, in your document, it is adviced 
to make the description blah blah and mandatory to be an Ark Linux packaged 
like explaned in the Ark Linux Packaging Rules chapter 3.1, and I could add 
"For more information consult the Ark Linux Packaging How To", etc and both 
documents should be in the Ark Linux Development Documentation.

> What do you think Pupeno?
I have just taken a fast look to it and it seems nice...
One thing, when formating the document, try to use styles, Like "Standard" 
"Document Title", "Heading 1", "Heading 2" like I did in my document (latter 
we should use the same fonts (that is, the same style) and the documents will 
look similar.
See you!
- -- 
Pupeno: [email protected]
http://www.kde.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAEFRMtCepaMf3unIRAkC7AJ0fIQQmgJj/U3dHOq9gQgMZ9zcXFACdH5N9
6RX7xibcVMS370P2SumazB4=
=FapE
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.