Mail Archives: geda-user/2016/12/24/07:55:45
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--bptVmBCVscCrbwxQpp9h4m3RmDAvSxR3n
Content-Type: multipart/mixed; boundary="71UHxwdv51sQ1mvKXruX0mwG0iBdVqnaL"
From: "M. J. Everitt" <m DOT j DOT everitt AT iee DOT org>
To: geda-user AT delorie DOT com
Message-ID: <2778f2e7-cd44-7823-a80b-a6ca0635c9f8 AT iee DOT org>
Subject: Re: [geda-user] [pcb] Plans for Next Release of pcb
References: <CAJZxidDy5HcLZivqc5w+cnv716EFNLXKJdKXo+jDPMDVrJb2=Q AT mail DOT gmail DOT com>
<74d9e3df-7aaa-cb29-5584-8c52d19227b1 AT sbcglobal DOT net>
<CAJZxidDPsP4=dBHu=M-yZ7Lmo-kgo2z2jDpcZgD=dtwB4TdWog AT mail DOT gmail DOT com>
<585E6661 DOT 8070806 AT xs4all DOT nl>
<CAJXU7q_-K2ZHgsKXrP=NOs1XkW7DVgYw-d17+fSGWyjb=nD5Ew AT mail DOT gmail DOT com>
In-Reply-To: <CAJXU7q_-K2ZHgsKXrP=NOs1XkW7DVgYw-d17+fSGWyjb=nD5Ew AT mail DOT gmail DOT com>
--71UHxwdv51sQ1mvKXruX0mwG0iBdVqnaL
Content-Type: multipart/alternative;
boundary="------------D629C930E13535AF99B6ECA6"
This is a multi-part message in MIME format.
--------------D629C930E13535AF99B6ECA6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
As a prospective proxy maintainer for Gentoo, please let me know when
you roll a tarball, and I'll run through the Gentoo packaging process,
and do some preliminary build/run-testing and feed back.
I would second a more consistent version numbering system, as this makes
version-tracking easier for packagers too, so pcb v4 would indeed be a
good choice if settled upon!
Good luck, thanks, and keep us posted on the list :)
Michael.
On 24/12/16 12:23, Peter Clifton (petercjclifton AT googlemail DOT com) [via
geda-user AT delorie DOT com] wrote:
> 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 making the delete.
>
> Peter
>
> On 24 Dec 2016 12:16, "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl
> <mailto:bert DOT timmerman AT xs4all DOT nl>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>]" <geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>> wrote:
>
> Chad Parker (parker DOT charles AT gmail DOT com
> <mailto:parker DOT charles AT gmail DOT com>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>] wrote:
>
> There is a page on launchpad with a list of bugs to fix before
> the next release
> (https://launchpad.net/pcb/+milestone/next-bug-release
> <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 our 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 skip it this time for the purpose of
> getting the release out the door more quickly.
>
> Girvin-
> Slackware 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 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 net>
> <mailto:gherr375 AT sbcglobal DOT net
> <mailto:gherr375 AT sbcglobal DOT net>>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com> <mailto:geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>>]" <geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com> <mailto:geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>>> wrote:
>
>
>
> On 12/21/2016 05:43 AM, Chad Parker
> (parker DOT charles AT gmail DOT com <mailto:parker DOT charles AT gmail DOT com>
> <mailto:parker DOT charles AT gmail DOT com
> <mailto:parker DOT charles AT gmail DOT com>>) [via geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>
> <mailto:geda-user AT delorie DOT com
> <mailto:geda-user AT delorie DOT com>>] wrote:
>
> Hi pcb Devs-
>
>
> Regarding packaging, do we create packages for
> distributions,
> or do the distributions 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. Whatever was done in the
> past has
> worked fine for me. I have had no problems building the 1.=
8.2
> version from source. I do rebuild .rpm packages for some
> apps,
> such as LibreOffice and Slackware has an rpm extractor
> (rpm2cpio)
> that works for them, but I prefer to build from source to m=
ake
> sure all the dependencies are correct.
>
> Not that I have seen them in gEDA, but compile warnings
> make me
> nervous. 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
>
>
> Hi Chad,
>
> I moved all open bug reports listed to the pcb
> "future-bug-release"
> (https://launchpad.net/pcb/+milestone/future-bug-release
> <https://launchpad.net/pcb/+milestone/future-bug-release>) to get
> them "out of the way" and hope that they do not distract you
> anymore ;-)
>
> I will keep away from pushing to the "master" branch for the
> coming 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.
>
--------------D629C930E13535AF99B6ECA6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Ty=
pe">
</head>
<body text=3D"#000000" bgcolor=3D"#FFFFFF">
As a prospective proxy maintainer for Gentoo, please let me know
when you roll a tarball, and I'll run through the Gentoo packaging
process, and do some preliminary build/run-testing and feed back.<br>=
<br>
I would second a more consistent version numbering system, as this
makes version-tracking easier for packagers too, so pcb v4 would
indeed be a good choice if settled upon!<br>
<br>
Good luck, thanks, and keep us posted on the list :)<br>
<br>
Michael.<br>
<br>
<div class=3D"moz-cite-prefix">On 24/12/16 12:23, Peter Clifton
(<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:petercjclifto=
n AT googlemail DOT com">petercjclifton AT googlemail DOT com</a>) [via <a class=3D"moz=
-txt-link-abbreviated" href=3D"mailto:geda-user AT delorie DOT com">geda-user AT de=
lorie.com</a>] wrote:<br>
</div>
<blockquote
cite=3D"mid:CAJXU7q_-K2ZHgsKXrP=3DNOs1XkW7DVgYw-d17+fSGWyjb=3DnD5Ew AT mail.=
gmail.com"
type=3D"cite">
<div dir=3D"auto">Nice to hear work is going on with mainline pcb a=
s
well...
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">One thing prior to release. We ought to git rm
the debian directory that added to the repository.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">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.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">I checked this with our debian packagers some
while back to confirm, but never got around to making the
delete.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">Peter</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 24 Dec 2016 12:16, "Bert Timmerman =
(<a
moz-do-not-send=3D"true"
href=3D"mailto:bert DOT timmerman AT xs4all DOT nl">bert DOT timmerman AT xs4al=
l.nl</a>)
[via <a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</=
a>]"
<<a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</=
a>>
wrote:<br type=3D"attribution">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Chad
Parker (<a moz-do-not-send=3D"true"
href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank">=
parker DOT charles AT gmail DOT com</a>)
[via <a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ged=
a-user AT delorie DOT com</a>]
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
There is a page on launchpad with a list of bugs to fix
before the next release (<a moz-do-not-send=3D"true"
href=3D"https://launchpad.net/pcb/+milestone/next-bug-rel=
ease"
rel=3D"noreferrer" target=3D"_blank">https://launchpad.ne=
t/pcb/+mi<wbr>lestone/next-bug-release</a>),
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.<br>
<br>
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 our 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 skip it this time
for the purpose of getting the release out the door more
quickly.<br>
<br>
Girvin-<br>
Slackware 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 latest git version if you'd like a
copy.<br>
<br>
--Chad<br>
<br>
On Dec 21, 2016 5:58 PM, "Girvin R. Herr (<a
moz-do-not-send=3D"true"
href=3D"mailto:gherr375 AT sbcglobal DOT net" target=3D"_blank">=
gherr375 AT sbcglobal DOT net</a>
<mailto:<a moz-do-not-send=3D"true"
href=3D"mailto:gherr375 AT sbcglobal DOT net" target=3D"_blank">=
gherr375 AT sbcglobal DOT net</a><wbr>>)
[via <a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a>
<mailto:<a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a>><wbr>]"
<<a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a>
<mailto:<a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a>><wbr>>
wrote:<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 On 12/21/2016 05:43 AM, Chad Parker (<a
moz-do-not-send=3D"true"
href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank=
">parker DOT charles AT gmail DOT com</a><br>
=C2=A0 =C2=A0 <mailto:<a moz-do-not-send=3D"true"
href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank=
">parker DOT charles AT gmail DOT c<wbr>om</a>>)
[via <a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a><br>
=C2=A0 =C2=A0 <mailto:<a moz-do-not-send=3D"true"
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">g=
eda-user AT delorie DOT com</a>><wbr>]
wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Hi pcb Devs-<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Regarding packaging, do we crea=
te packages for
distributions,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 or do the distributions to that=
themselves?<br>
<br>
=C2=A0 =C2=A0 Chad,<br>
=C2=A0 =C2=A0 I am just a lowly user, but here is my 2-cent=
s:<br>
=C2=A0 =C2=A0 I run Slackware Linux, so I download the sour=
ce and
build my own<br>
=C2=A0 =C2=A0 Slackware installation package.=C2=A0 Whateve=
r was done in
the past has<br>
=C2=A0 =C2=A0 worked fine for me.=C2=A0 I have had no probl=
ems building
the 1.8.2<br>
=C2=A0 =C2=A0 version from source.=C2=A0 I do rebuild .rpm =
packages for
some apps,<br>
=C2=A0 =C2=A0 such as LibreOffice and Slackware has an rpm =
extractor
(rpm2cpio)<br>
=C2=A0 =C2=A0 that works for them, but I prefer to build fr=
om source
to make<br>
=C2=A0 =C2=A0 sure all the dependencies are correct.<br>
<br>
=C2=A0 =C2=A0 Not that I have seen them in gEDA, but compil=
e
warnings make me<br>
=C2=A0 =C2=A0 nervous.=C2=A0 There is no reason they cannot=
and should
not be fixed.<br>
=C2=A0 =C2=A0 It's a sign of lack of quality.<br>
=C2=A0 =C2=A0 Compile errors are fatal frustrations.<br>
<br>
=C2=A0 =C2=A0 Thanks and good luck.<br>
=C2=A0 =C2=A0 Girvin Herr<br>
<br>
<br>
</blockquote>
Hi Chad,<br>
<br>
I moved all open bug reports listed to the pcb
"future-bug-release" (<a moz-do-not-send=3D"true"
href=3D"https://launchpad.net/pcb/+milestone/future-bug-rel=
ease"
rel=3D"noreferrer" target=3D"_blank">https://launchpad.net/=
pcb/+mi<wbr>lestone/future-bug-release</a>)
to get them "out of the way" and hope that they do not
distract you anymore ;-)<br>
<br>
I will keep away from pushing to the "master" branch for the
coming 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.<br>=
<br>
Please keep us informed how this "dry run" works out.<br>
<br>
Kind regards,<br>
<br>
Bert Timmerman.<br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------D629C930E13535AF99B6ECA6--
--71UHxwdv51sQ1mvKXruX0mwG0iBdVqnaL--
--bptVmBCVscCrbwxQpp9h4m3RmDAvSxR3n
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBCAAGBQJYXnAAAAoJEN7KWvRhIveDMqcP/jsoGi2AWq1NFafwOZ0UQxCj
Ttpqve+YKmYxMVcR14QGDuvyRBXhRQKh25iwls/SlIAsqBiw/++fjm8SuorzMqoP
4flbDL41Tb9po9Xm50NwEEsgRNIfN58F1Uj4bpOKQVJ75rUN5anZqAQjuCmcNNVe
Eb+ELeaXrUY22TShdXWhsNftO01lxeDUMo6lY6WOan3MN8tqXBvEy0/t/iK+tBmo
V3Vb9Vu6vfNBwgzu1fPBu6qi9sZPyLfwuLwhAQKAugpTNBrrQoSpvaurrvCMZMKt
+EpKCSaI1p4JcFTJIpWA3FD5tRj+etNr8/sUPxdWqbyFnn9t9VFz6BKlHYSvlAmu
B3eGqFpOaMqirZxa3zv17Mla/bdx5uMbBLCZ3tkZCG7hyFdcNd6gOHGg0qYvBVWy
xVrUZqJYRybbCjgtSrLlv9dE68z/QQCvn6npZgaHxbRb1EVnyPF3790w1EUVqAhv
HdWjf1/Rh5UCD19w2v3cGVv+yHRCmk1SDzMS3r2ewYBhDSQ3LB8spHEXLLGK4VQr
m6XiR4rUR5izZ++O96XkIsNPLVTvDfEQUWQvVFF6AmWlh+rUMertbMzNEoxHKXp7
S8kYcOrF8EqK6uAZVYsbkWx5HLb/qC5Jj7C7AruFI0KsQfxK4Wln08wFCU1sdHhL
tkoZQkLxaxvcalm0bvZc
=G0WR
-----END PGP SIGNATURE-----
--bptVmBCVscCrbwxQpp9h4m3RmDAvSxR3n--
- Raw text -