Thanks for the links to relevant current developer documentation. I'll
keep an eye on those guidelines.

I have to say that even having been an avid PLD user for 10+ years the
lack of clear easy to find documentation (and the amount of outdated,
irrelevant and contradictory documentation floating around in dozens
of locations) is making me dizzy.

I have subscribed to the cvs commit list and will try to keep up with
what's current that way.

Caleb

2010/3/29 Elan Ruusamäe <g...@pld-linux.org>:
> On Monday 29 March 2010 14:48:05 Caleb Maclennan wrote:
>> Question about log messages. I noticed after I committed a bump to the
>> version of hugin last night that most log messages for spec file
>> commits start with a leading dash. Does this have a special meaning or
>> is it just convention that I should follow or did I fail in some other
>> way?
>
> it is explained in here:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/HACKING
>
> also you mind find this useful:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/BuildRequires.txt
>
> and these two (depending on your language preference)
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/devel-hints-en.txt
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/PLD-doc/devel-hints-pl.txt
>
> however, these may not be exactly up to date, most of the knowledge comes imho
> via monitoring of spec commits.
>
> and when creating new .specs, there are somewhat useful templates:
> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/template-specs/
>
> --
> glen
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en

Reply via email to