Mail Archives: geda-user/2016/12/24/07:24:43
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f
|
| X-Recipient: | geda-user AT delorie DOT com
|
| X-Original-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed;
|
| d=googlemail.com; s=20161025;
|
| h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
|
| bh=Fy+nZahpVuG+h1x8bmam/EG7HSh8haK7pD9lN5dM3lI=;
|
| b=pv2linA/+lfdofmDK/6m3PixEh87k2qHiY2mDJ39c3B3cJU06fiwUIh2OBuaT1qHXE
|
| qSEdnXuBR5x01+2RbQJFjAPhHhYXTK/lUrlOPbkZg7k4pLEbgFRQ7R+fTE8MCbeoO4J1
|
| bSS0Ig5Z2t0MJhPIrnoFw/biqLxF/F2p3DJ9/fInNT3vOSANW/F8a9Pi+mFF6xcP9abP
|
| 1CwVuDvc2R0mgqvYYX8tiZbnnHRw6BJ6mzMWiUe2fOBxlpRJ63pp30ZwQ1dChdCJJbH5
|
| jiZvE9fUKbSdKgMEe5XYWnEuPhEl9LzufOi6NM5joWUzN5GiW4IoZ1S74mVKH9qI+pIN
|
| za1A==
|
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed;
|
| d=1e100.net; s=20161025;
|
| h=x-gm-message-state:mime-version:in-reply-to:references:from:date
|
| :message-id:subject:to;
|
| bh=Fy+nZahpVuG+h1x8bmam/EG7HSh8haK7pD9lN5dM3lI=;
|
| b=GOeUIYXppys4dxQkOlCIlxHSOGwwdljF8YAki++gUxnN37mmGsMB/kXxnrCmc6vU7N
|
| TpurzwCtjpuMCiYAMjUZDr3TnQSheJ0e951da6y9iglL7Y/zCzSQ7i+uNvy7z87ii0RY
|
| H5WA9x5L8AgIkI2H/qTGSik8Cq7TqQPIAAszrG2owa0wUDll3mVfhlW9U8+nhJLAGiLz
|
| KWf/Er2Fjo1w8dPh1v+p1PyNKDhRUZlaveZt12kD9FEaSuwA/ibKbKGEMogM8FhYRHx2
|
| 5btG1YYNRAxYfdmwpdDRb/eToK5+A6K07Le/z1WFxgaOS76MC8fNHzPr2jq8g5lKXYuw
|
| IkIw==
|
| X-Gm-Message-State: | AIkVDXIa9+Cu3Ui8mhIEHCdJ7lYBvJ3EurkqwVfampTdzgZJo1pT4xqEPezzYHoAaaeNd02FbHPcMqqj5KIHzw==
|
| X-Received: | by 10.55.82.69 with SMTP id g66mr18916082qkb.304.1482582210703;
|
| Sat, 24 Dec 2016 04:23:30 -0800 (PST)
|
| MIME-Version: | 1.0
|
| In-Reply-To: | <585E6661.8070806@xs4all.nl>
|
| 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>
|
| From: | "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
|
| Date: | Sat, 24 Dec 2016 12:23:29 +0000
|
| Message-ID: | <CAJXU7q_-K2ZHgsKXrP=NOs1XkW7DVgYw-d17+fSGWyjb=nD5Ew@mail.gmail.com>
|
| Subject: | Re: [geda-user] [pcb] Plans for Next Release of pcb
|
| To: | gEDA User Mailing List <geda-user AT delorie DOT com>
|
| Reply-To: | geda-user AT delorie DOT com
|
| Errors-To: | nobody AT delorie DOT com
|
| X-Mailing-List: | geda-user AT delorie DOT com
|
| X-Unsubscribes-To: | listserv AT delorie DOT com
|
--001a114a821804f72a05446692e2
Content-Type: text/plain; charset=UTF-8
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) [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] 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), 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>) [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:
>>
>>
>>
>> On 12/21/2016 05:43 AM, 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:
>>
>> 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 make
>> 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) 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.
>
--001a114a821804f72a05446692e2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">Nice to hear work is going on with mainline pcb as 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 m=
aking 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 href=3D"mailto:bert DOT timmerman AT xs4a=
ll.nl">bert DOT timmerman AT xs4all DOT nl</a>) [via <a href=3D"mailto:geda-user AT delor=
ie.com">geda-user AT delorie DOT com</a>]" <<a href=3D"mailto:geda-user AT de=
lorie.com">geda-user AT delorie DOT com</a>> wrote:<br type=3D"attribution"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Chad Parker (<a href=3D"mailto:parker DOT charles AT g=
mail.com" target=3D"_blank">parker DOT charles AT gmail DOT com</a>) [via <a href=3D"m=
ailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] w=
rote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
There is a page on launchpad with a list of bugs to fix before the next rel=
ease (<a href=3D"https://launchpad.net/pcb/+milestone/next-bug-release" rel=
=3D"noreferrer" target=3D"_blank">https://launchpad.net/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 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.<br>
<br>
Girvin-<br>
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.<br>
<br>
--Chad<br>
<br>
On Dec 21, 2016 5:58 PM, "Girvin R. Herr (<a href=3D"mailto:gherr375 AT s=
bcglobal.net" target=3D"_blank">gherr375 AT sbcglobal DOT net</a> <mailto:<a hr=
ef=3D"mailto:gherr375 AT sbcglobal DOT net" target=3D"_blank">gherr375 AT sbcglobal DOT n=
et</a><wbr>>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_b=
lank">geda-user AT delorie DOT com</a> <mailto:<a href=3D"mailto:geda-user AT delo=
rie.com" target=3D"_blank">geda-user AT delorie DOT com</a>><wbr>]" <<a=
href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie.=
com</a> <mailto:<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blan=
k">geda-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 href=3D"mailto:parker=
.charles AT gmail DOT com" target=3D"_blank">parker DOT charles AT gmail DOT com</a><br>
=C2=A0 =C2=A0 <mailto:<a 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 href=3D"mailto:g=
eda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a><br>
=C2=A0 =C2=A0 <mailto:<a href=3D"mailto:geda-user AT delorie DOT com" target=3D=
"_blank">geda-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 create 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-cents:<br>
=C2=A0 =C2=A0 I run Slackware Linux, so I download the source and build my =
own<br>
=C2=A0 =C2=A0 Slackware installation package.=C2=A0 Whatever was done in th=
e past has<br>
=C2=A0 =C2=A0 worked fine for me.=C2=A0 I have had no problems building the=
1.8.2<br>
=C2=A0 =C2=A0 version from source.=C2=A0 I do rebuild .rpm packages for som=
e apps,<br>
=C2=A0 =C2=A0 such as LibreOffice and Slackware has an rpm extractor (rpm2c=
pio)<br>
=C2=A0 =C2=A0 that works for them, but I prefer to build from source to mak=
e<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 compile 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&quo=
t; (<a href=3D"https://launchpad.net/pcb/+milestone/future-bug-release" 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 th=
at they do not distract you anymore ;-)<br>
<br>
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.<br>
<br>
Please keep us informed how this "dry run" works out.<br>
<br>
Kind regards,<br>
<br>
Bert Timmerman.<br>
</blockquote></div></div>
--001a114a821804f72a05446692e2--
- Raw text -