Am 11.01.2014 20:51, schrieb Olaf Radicke: ... > Sounds is confusing for me. I think it is better we create a separate > repos for (markdown) howtos and the other project can do link this. So > tntnet (rpm) packet can has a dependency with this howto packet and the > website packet too. > > > Olaf I moved the howtos from tntnet-homepage to the projects for good reason. Documentation about tntnet belongs to tntnet. And I still feel that it is a good solution.
The tntnet-homepage publish those documents on the web. So part of the build process is to collect the documentation from the projects. I don't think it is a good idea to create a new repo for markdown documentation. Note that there are man pages too. Do you expect another repo for man pages? I don't. It is fine to include the full tntnet documentation in the tntnet dist package. That does not mean, that the documentation needs to be in the same rpm. It is very common to create multiple rpms from a single dist, e.g. tntnet, tntnet-devel and tntnet-doc. Tommi ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
