There is a page on launchpad with a list of bugs to fix before the next r= elease (h= ttps://launchpad.net/pcb/+milestone/next-bug-release), many of which ha= ve been addressed. Unless there are things like fixing warnings, I think we= ought to push the rest of them to a future bug release for the sake of get= ting a release out quickly.

Regarding versioning, I thin= k that generally for major releases, a release candidate and a testing peri= od is a good idea. But I wonder, how many of our users are already using th= e git head? If most people are, then we've already basically had a test= ing period. When we put out a release candidate, do distributions package a= nd distribute it? So, basically, would we get a larger testing audience by = doing so? If not, then maybe we should just skip it this time for the purpo= se of getting the release out the door more quickly.

Girvin-
Slackwa= re was my distro of choice until I had to start using a work computer, so I= actually know how to build a Slackware package. But pcb isn't part of = the Slackware distribution. You can get an older version of pcb from sbopkg= . I think I still have script lying around to build a package from the late= st git version if you'd like a copy.=C2=A0

<= /div>

--Chad

On Dec 21, 2016 5:58 PM, "Gir= vin R. Herr (gh= err375 AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

<= br>
On 12/21/2016 05:43 AM, Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] wrote= :

Hi pcb Devs-

Regarding packaging, do we create packages for distributions, or do the dis= tributions to that themselves?

Chad,
I am just a lowly user, but here is my 2-cents:
I run Slackware Linux, so I download the source and build my own Slackware = installation package.=C2=A0 Whatever was done in the past has worked fine f= or me.=C2=A0 I have had no problems building the 1.8.2 version from source.= =C2=A0 I do rebuild .rpm packages for some apps, such as LibreOffice and Sl= ackware has an rpm extractor (rpm2cpio) that works for them, but I prefer t= o build from source to make sure all the dependencies are correct.

Not that I have seen them in gEDA, but compile warnings make me nervous.=C2= =A0 There is no reason they cannot and should not be fixed. It's a sign= of lack of quality.
Compile errors are fatal frustrations.

Thanks and good luck.
Girvin Herr

--047d7bf10b4e0be08005443fbe46--