On 04/11/15 10:28, Raffi Enficiaud wrote: > Le 04/11/15 09:50, Gianfranco Costamagna a écrit : >> Hi, generating debian files from cmake is not trivial, and I'm not >> sure I can answer here. > > Hi, > > Thank you for your reply! Would you please tell me what are the > difficulties? I have more the developer hat, and not the packager one, > and to me it is a bunch of "install" commands in cmake (with proper > components and location), and "make" + "make package".
Hi! I'm a newbie here (no mentor!), and possibly get it all wrong. That said, my gut feeling is that this kind of functionality isn't really helpful. I have seen some examples on the RPM side. The basic problem is actually illustrated by Gianfranco's reply. Packaging is taking place in a community, in this case Debian. The community sets up rules makes and makes reviews. The rules, tools and processes evolves over time. At this point it is clear that you haven't really understood the community to the point you can create a package which conforms to the rules. Packaging is so much more than lumping a bunch of files in a container. BTW, splitting the /usr hierarchy into sub-packages is IMHO one of the smaller problems in this context. The first question you need to answer is if your generated packages conforms to the Debian Policy Manual. Do they? If they do, this is something new. I have yet not seen an automatically generated package which conforms to the given rules (Fedora experience). And that experience might be the reason no-one else replies :) Cheers! --alec PS Not understanding the Policy Manual is actually also my problem... DS
