Suggestions for package naming/split

Hi, I'm writing some PHP classes that I want to submit/upload to PEAR (obviously, using PEPr, votes, etc..). These classes are focused in Debian, I'm currently splitting them in two parts: - User: Debian_Apt, Debian_File and Debian_BTS -Bug Tracking System- - Devel: I don't have any classes currently but I'm thinking in writing a Debian package creator and/or a package validator. But I have some questions for releasing these packages: I can release a Debian_Utils package that will have both parts (User and Devel), but in the case of Debian_BTS it depends on another package (Mail[2] package) and the Devel classes depend on another package (File_Archive). So, my question is: is there any conventions for splitting packages? Should I split the packages by their dependencies so I should create many PEPr(s): * Package: Debian_Apt * Package: Debian_File * Package: Debian_BTS * Package: Debian_Devel * Package: Debian_Lintian Or should I create just one package (Debian_Utils) and add a lot of dependencies to it and don't care if a user needs to download Mail package also if Debian_BTS is not going to be used by the user?. Pablo [1] http://lintian.debian.org/ -- Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx) Cel: (044-55) 2689-6351 Fingerprint: 5973 0F10 543F 54AE 1E41 EC81 0840 A10A 74A4 E5C0 http://www.pablo.com.mx http://www.debianmexico.org

Attachment: [application/pgp-signature] This is a digitally signed message part signature.asc