Re: Suggestions for package naming/split

Pablo Fischer wrote:

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: 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): 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/

I would say, split the package based on its usage... -Philippe