Mail Archives: geda-user/2016/12/22/09:05:56
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=gmail.com; s=20161025;
|
| h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
|
| bh=BxB0tkHkwOphiPqyDmmzi6unQvtIsCXID/xor17qE3Y=;
|
| b=IazRC2h5cZHfXyTifIEq9tMqDXV7HcCoTIuttmev7fQSg8T2HD3klmGTdLM2B2oZWH
|
| pIrHT0naRqzv/CzFEBCoRngrKC4HIc0mGRZlPUDPPLnhUTSU4wZTMg4cK7IIzTAkEiLM
|
| yb3jc1T3A1hqPGJvxnqPG1chCs61oXh/lIo1vfdHIGlCrzJsUQ15WBIj5wGVfFr4a3A0
|
| B+cl8v0NedmKWxLVie7oumPrIXyB05D4yaS2s1FfUrYWvh23BcQbD3gBujnmCY2WUuVK
|
| QfNZw34m/8hx1ENI9XieqzgZqQmjBwanZhYF8uou8yUUdVtKbg4IJs6GCcdDy8Q0ibkK
|
| j9Tg==
|
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=BxB0tkHkwOphiPqyDmmzi6unQvtIsCXID/xor17qE3Y=;
|
| b=m/x7O3Zvj9MOA5AHED2c+lmWTZNVePVn/fydX1hhs+qKNH1WxzQNKEV4uiT1qn/YK4
|
| Jsde6ST4+/h6dAz9o34cek1am82xOs/GYxKA8MS7PRgYaGjLsj2gsL6h7zU5iLqE9LH6
|
| QUvYL+eVz2TWUgvS8VNc4FIe2zy99ZzG0iUO6mectW9k3HAeAlUnjJCbNhlgZ4PPL8Qi
|
| wy085oVw7WsZfdmsvVeNYfsCRPIeEzw79/5E3fhU1kSQEG/rJKufnsvVBylLnmfSpj+L
|
| jy30ouH9x732vdrUbeS4KK8rihRUC6DGc8skIsCnCAn9UhxNxrL51yVosK495BRGYm1P
|
| QHnw==
|
X-Gm-Message-State: | AIkVDXL+GIpnXxBNBetWbp+2h5vrZCDu88XHKjrG/mzaNnIVi7nOgxsuNK96VlUZ/GMu7hzrDqeFFk8U6uInWw==
|
X-Received: | by 10.194.109.168 with SMTP id ht8mr9329968wjb.36.1482415445628;
|
| Thu, 22 Dec 2016 06:04:05 -0800 (PST)
|
MIME-Version: | 1.0
|
In-Reply-To: | <74d9e3df-7aaa-cb29-5584-8c52d19227b1@sbcglobal.net>
|
References: | <CAJZxidDy5HcLZivqc5w+cnv716EFNLXKJdKXo+jDPMDVrJb2=Q AT mail DOT gmail DOT com>
|
| <74d9e3df-7aaa-cb29-5584-8c52d19227b1 AT sbcglobal DOT net>
|
From: | "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
|
Date: | Thu, 22 Dec 2016 09:04:05 -0500
|
Message-ID: | <CAJZxidDPsP4=dBHu=M-yZ7Lmo-kgo2z2jDpcZgD=dtwB4TdWog@mail.gmail.com>
|
Subject: | Re: [geda-user] [pcb] Plans for Next Release of pcb
|
To: | 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
|
--047d7bf10b4e0be08005443fbe46
Content-Type: text/plain; charset=UTF-8
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) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
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
> 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
--047d7bf10b4e0be08005443fbe46
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div dir=3D"auto"><div dir=3D"auto"></div><div dir=3D"auto=
">There is a page on launchpad with a list of bugs to fix before the next r=
elease (<a href=3D"https://launchpad.net/pcb/+milestone/next-bug-release">h=
ttps://launchpad.net/pcb/+milestone/next-bug-release</a>), 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. <br><br></div><div>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.<br></div><div dir=3D"a=
uto"></div><div dir=3D"auto"><br></div><div dir=3D"auto">Girvin-<br>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><div dir=3D"auto"><br><=
/div><div>--Chad<br></div><div dir=3D"auto"><div class=3D"gmail_extra" dir=
=3D"auto"><br><div class=3D"gmail_quote">On Dec 21, 2016 5:58 PM, "Gir=
vin R. Herr (<a href=3D"mailto:gherr375 AT sbcglobal DOT net" target=3D"_blank">gh=
err375 AT sbcglobal DOT net</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com" tar=
get=3D"_blank">geda-user AT delorie DOT com</a>]" <<a href=3D"mailto:geda-=
user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>> wrote:<br=
type=3D"attribution"><blockquote class=3D"gmail-m_-4878331601821816790quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div class=3D"gmail-m_-4878331601821816790quoted-text"><=
br>
<br>
On 12/21/2016 05:43 AM, Chad Parker (<a href=3D"mailto:parker DOT charles AT gmail=
.com" target=3D"_blank">parker DOT charles AT gmail DOT com</a>) [via <a href=3D"mailt=
o:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] wrote=
:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi pcb Devs-<br>
<br>
<br><div class=3D"gmail-m_-4878331601821816790quoted-text">
Regarding packaging, do we create packages for distributions, or do the dis=
tributions to that themselves?<br>
</div></blockquote>
Chad,<br>
I am just a lowly user, but here is my 2-cents:<br>
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.<br>
<br>
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.<br>
Compile errors are fatal frustrations.<br>
<br>
Thanks and good luck.<br>
Girvin Herr<br>
<br>
</blockquote></div><br></div></div></div>
</div>
--047d7bf10b4e0be08005443fbe46--
- Raw text -