Mail Archives: geda-user/2016/12/24/18:58:39
--001a114428c4361ba90544704174
Content-Type: text/plain; charset=UTF-8
Is the reason people want to skip to version 4 just because of that fork
that claimed version 3.x? If so, we could still use the 2.x.x series before
having to worry about the naming collision, and then skip to 4.0.0. Or is
it that we want to tell prospective users that ours is better by having a
higher version number?
DJ-
I agree that there haven't been any changes that would break backward
compatibility, but sometimes you just have to make a clean break, like when
the kernel went to 3.0.0.
Bert-
Thanks, I can be a little OCD sometimes, and I do like things to be neat
and clean! Particularly when it comes to plans.
I sort of assumed that we would either have the code sprint earlier, or not
have one this month since the last Sunday of the month (tomorrow) is
Christmas day and I imagine that a lot of people will be observing that
holiday.
I'll run through the release procedure that Dan pointed out sometime in the
next couple of days and let folks know how things go. I think there are at
least a couple of compile warnings on my Mac that will need to be fixed.
Cheers, and have a good holiday to all those who are celebrating.
--Chad
On Sat, Dec 24, 2016 at 3:01 PM, Girvin Herr (
girvin_herr+gherr_lists AT fastmail DOT com) [via geda-user AT delorie DOT com] <
geda-user AT delorie DOT com> wrote:
>
>
> On 12/24/2016 04:50 AM, M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via
> geda-user AT delorie DOT com] wrote:
>
> 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.
>
> If wanted, I can do the same for a Slackware Linux package. I am
> currently running Slackware 14.1 (k3.10.103), but I have a copy of the
> latest 14.2 and plan to install it early next year. The only change I can
> see is that the package architecture went from i486 in 14.1 to i586 in
> 14.2, but that is trivial. Of course, the dependencies have changed.
>
> Another option would be to contact the SlackBuilds.org pcb package
> maintainer, Felix Pfeifer: pfeifer [dot] felix [at] googlemail [dot] com
> He might be willing to do this task and put the resulting packages on
> SlackBuilds.
>
> geda-gaf on SlackBuilds.org seems to be maintained by a different
> maintainer, Stephen Van Berg: stephen_van_berg at earlicker dot com
>
> 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!
>
> Consistency, yes. But the form doesn't matter for Slackware packaging.
> x.y.z is just as fine as yyyymmdd. The only caveat is that dashes may not
> be used in the version string. I usually change them to underscores or
> remove them entirely if in yyyy-mm-dd.
>
> Girvin Herr
>
>
> 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
>
>
>
--001a114428c4361ba90544704174
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>Is the reason people want to skip to v=
ersion 4 just because of that fork that claimed version 3.x? If so, we coul=
d still use the 2.x.x series before having to worry about the naming collis=
ion, and then skip to 4.0.0. Or is it that we want to tell prospective user=
s that ours is better by having a higher version number?<br><br>DJ-<br></di=
v>I agree that there haven't been any changes that would break backward=
compatibility, but sometimes you just have to make a clean break, like whe=
n the kernel went to 3.0.0.<br><br></div>Bert-<br></div>Thanks, I can be a =
little OCD sometimes, and I do like things to be neat and clean! Particular=
ly when it comes to plans. <br><br>I sort of assumed that we would either h=
ave the code sprint earlier, or not have one this month since the last Sund=
ay of the month (tomorrow) is Christmas day and I imagine that a lot of peo=
ple will be observing that holiday.<br><br></div><div>I'll run through =
the release procedure that Dan pointed out sometime in the next couple of d=
ays and let folks know how things go. I think there are at least a couple o=
f compile warnings on my Mac that will need to be fixed.<br><br></div><div>=
Cheers, and have a good holiday to all those who are celebrating.<br></div>=
<div>--Chad<br></div><div><br><br></div><br></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Sat, Dec 24, 2016 at 3:01 PM, Girvin He=
rr (<a href=3D"mailto:girvin_herr%2Bgherr_lists AT fastmail DOT com">girvin_herr+g=
herr_lists AT fastmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">=
geda-user AT delorie DOT com</a>] <span dir=3D"ltr"><<a href=3D"mailto:geda-use=
r AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>></span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
<p><br>
</p>
<br>
<div class=3D"m_-2844227609031222907moz-cite-prefix">On 12/24/2016 04:5=
0 AM, M. J. Everitt
(<a class=3D"m_-2844227609031222907moz-txt-link-abbreviated" href=3D"=
mailto:m DOT j DOT everitt AT iee DOT org" target=3D"_blank">m DOT j DOT everitt AT iee DOT org</a>) [via=
<a class=3D"m_-2844227609031222907moz-txt-link-abbreviated" href=3D"mailto=
:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] wrote:=
<br>
</div>
<blockquote type=3D"cite">
=20
As a prospective proxy maintainer for Gentoo, please let me know
when you roll a tarball, and I'll run through the Gentoo packagin=
g
process, and do some preliminary build/run-testing and feed back.<br>
<br>
</blockquote></span>
If wanted, I can do the same for a Slackware Linux package.=C2=A0 I am
currently running Slackware 14.1 (k3.10.103), but I have a copy of
the latest 14.2 and plan to install it early next year.=C2=A0 The only
change I can see is that the package architecture went from i486 in
14.1 to i586 in 14.2, but that is trivial.=C2=A0 Of course, the
dependencies have changed.<br>
<br>
Another option would be to contact the SlackBuilds.org pcb package
maintainer, Felix Pfeifer:=C2=A0 pfeifer [dot] felix [at] googlemail
[dot] com<br>
He might be willing to do this task and put the resulting packages
on SlackBuilds.<br>
<br>
geda-gaf on SlackBuilds.org seems to be maintained by a different
maintainer, Stephen Van Berg:=C2=A0 stephen_van_berg at earlicker dot c=
om<span class=3D""><br>
<br>
<blockquote type=3D"cite"> I would second a more consistent version num=
bering
system, as this makes version-tracking easier for packagers too,
so pcb v4 would indeed be a good choice if settled upon!<br>
</blockquote></span>
Consistency, yes.=C2=A0 But the form doesn't matter for Slackware
packaging.=C2=A0 x.y.z is just as fine as yyyymmdd.=C2=A0 The only cave=
at is
that dashes may not be used in the version string.=C2=A0 I usually chan=
ge
them to underscores or remove them entirely if in yyyy-mm-dd.<br>
<br>
Girvin Herr<span class=3D""><br>
<br>
<blockquote type=3D"cite"> <br>
Good luck, thanks, and keep us posted on the list :)<br>
<br>
Michael.<br>
<br>
<div class=3D"m_-2844227609031222907moz-cite-prefix">On 24/12/16 12:2=
3, Peter Clifton (<a class=3D"m_-2844227609031222907moz-txt-link-abbreviate=
d" href=3D"mailto:petercjclifton AT googlemail DOT com" target=3D"_blank">petercjc=
lifton AT googlemail DOT com</a><wbr>)
[via <a class=3D"m_-2844227609031222907moz-txt-link-abbreviated" hr=
ef=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com=
</a>]
wrote:<br>
</div>
<blockquote type=3D"cite">
<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 making the
delete.</div>
<div dir=3D"auto"><br>
</div>
<div dir=3D"auto">Peter</div>
</div>
<br>
</blockquote>
</blockquote>
<br>
</span></div>
</blockquote></div><br></div>
--001a114428c4361ba90544704174--
- Raw text -