Nice to hear work is going on with mainline pcb as well..= .

One thing prior to release. = We ought to git rm the debian directory that added to the repository.

This matches preferred distro= policy, and makes life easier for the official packagers (so they can use = our sources directly without having to repackage them to remove the debian = dir.

I checked this with= our debian packagers some while back to confirm, but never got around to m= aking the delete.

Peter<= /div>

On 24 = Dec 2016 12:16, "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com] w= rote:

There is a page on launchpad with a list of bugs to fix before the next rel= ease (https://launchpad.net/pcb/+milestone= /next-bug-release), many of which have 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 getting a release out quickly.

Regarding versioning, I think that generally for major releases, a release = candidate and a testing period is a good idea. But I wonder, how many of ou= r users are already using the git head? If most people are, then we've = already basically had a testing period. When we put out a release candidate= , do distributions package and distribute it? So, basically, would we get a= larger testing audience by doing so? If not, then maybe we should just ski= p it this time for the purpose of getting the release out the door more qui= ckly.

Girvin-
Slackware was my distro of choice until I had to start using a work compute= r, so I actually know how to build a Slackware package. But pcb isn't p= art 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 t= he latest git version if you'd like a copy.

--Chad

On Dec 21, 2016 5:58 PM, "Girvin R. Herr (gherr375 AT sbcglobal DOT net <mailto:gherr375 AT sbcglobal DOT n= et>) [via geda-user AT delorie DOT com <mailto:geda-user AT delorie DOT com>]" <geda-user AT delorie.= com <mailto:geda-user AT delorie DOT com>> wrote:

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

=C2=A0 =C2=A0 =C2=A0 =C2=A0 Hi pcb Devs-

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

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

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

=C2=A0 =C2=A0 Thanks and good luck.
=C2=A0 =C2=A0 Girvin Herr

Hi Chad,

I moved all open bug reports listed to the pcb "future-bug-release&quo= t; (https://launchpad.net/pcb/+milestone= /future-bug-release) to get them "out of the way" and hope th= at they do not distract you anymore ;-)

I will keep away from pushing to the "master" branch for the comi= ng weeks (busy day job, no holidays, most likely no pcb monthly code sprint= this last Sunday of the month (December 25th)) so you can start your "= ;dry run" any time you like.

Please keep us informed how this "dry run" works out.

Kind regards,

Bert Timmerman.

--001a114a821804f72a05446692e2--