Mail Archives: geda-user/2015/09/15/09:58:37
--089e01493fa82b98a7051fc99379
Content-Type: text/plain; charset=UTF-8
On Tue, Sep 15, 2015 at 9:50 PM, Peter Stuge (peter AT stuge DOT se) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> Juergen Harms (juergen DOT harms AT unige DOT ch) [via geda-user AT delorie DOT com] wrote:
> > distributions have the policy of strictly limiting the distributed
> > software to stable versions of upstream packages.
>
> Yes, it's really sad that distributions offer so little added value.
> There is a huge potential for distribution differentiation in
> following upstreams much more closely. Oh well.
>
I can speak for the Fedora situation, but this probably applies equally
well to several distros.
Fedora with it's policy of "Freedom, Friends, Features, *First*" has a
policy of staying current with upstream as much as possible. They are very
willing to run with newer bleeding-edge versions. Many official packages
in Fedora are compiled from source that came straight out of a git repo,
and there's a culture of pushing patches upstream.
Packaging work doesn't happen by itself. It's a fair bet the reason Fedora
22 is still at 1.8.2 is because there's no Fedora user who knows packaging,
*and* who uses geda-gaf, *and* who has stood up to do the packaging.
FWIW, Fedora provides a no-cost build architecture called COPR which builds
packages from source, and serves the packages out to testers and the
public. This is used by one KiCad user to build and serve dev-branch
versions of KiCad for Fedora. The same could be done with geda-gaf.
http://developerblog.redhat.com/2014/03/11/intro-coprs/
https://fedorahosted.org/copr/wiki/UserDocs
https://copr.fedoraproject.org/coprs/mangelajo/kicad/
If the project would like to see a more recent version of geda-gaf go into
Fedora (or any other distro that welcomes bleeding edge), someone will have
to step up and do the packaging. From my past experience with other
packages, Fedora will welcome the effort.
Mitch.
--089e01493fa82b98a7051fc99379
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div class=3D"gmail_quote">On Tue, Sep 15, 2015 at 9:50 PM, Peter Stuge (<a=
href=3D"mailto:peter AT stuge DOT se">peter AT stuge DOT se</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-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT c=
om</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
>Juergen Harms (<a href=3D"mailto:juergen DOT harms AT unige DOT ch">juergen DOT harms AT uni=
ge.ch</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie.=
com</a>] wrote:<br>
> distributions have the policy of strictly limiting the distributed<br>
> software to stable versions of upstream packages.<br>
<br>
</span>Yes, it's really sad that distributions offer so little added va=
lue.<br>
There is a huge potential for distribution differentiation in<br>
following upstreams much more closely. Oh well.<br></blockquote><div><br>I =
can speak for the Fedora situation, but this probably applies equally well =
to several distros.<br><br>Fedora with it's policy of "<span class=
=3D"st"><span class=3D"f"></span>Freedom, Friends, Features, <em>First</em>=
" </span>has a policy of staying current with upstream as much as poss=
ible.=C2=A0 They are very willing to run with newer bleeding-edge versions.=
=C2=A0 Many official packages in Fedora are compiled from source that came =
straight out of a git repo, and there's a culture of pushing patches up=
stream. =C2=A0 <br><br>Packaging work doesn't happen by itself.=C2=A0 I=
t's a fair bet the reason Fedora 22 is still at 1.8.2 is because there&=
#39;s no Fedora user who knows packaging, <i>and</i> who uses geda-gaf, <i>=
and</i> who has stood up to do the packaging.<br><br>FWIW, Fedora provides =
a no-cost build architecture called COPR which=20
builds packages from source, and serves the packages out to testers and=20
the public.=C2=A0 This is used by one KiCad user to build and serve=20
dev-branch versions of KiCad for Fedora.=C2=A0 The same could be done with=
=20
geda-gaf.<br><br>=C2=A0 <a href=3D"http://developerblog.redhat.com/2014/03/=
11/intro-coprs/">http://developerblog.redhat.com/2014/03/11/intro-coprs/</a=
><br>=C2=A0 <a href=3D"https://fedorahosted.org/copr/wiki/UserDocs">https:/=
/fedorahosted.org/copr/wiki/UserDocs</a><br>=C2=A0 <a href=3D"https://copr.=
fedoraproject.org/coprs/mangelajo/kicad/">https://copr.fedoraproject.org/co=
prs/mangelajo/kicad/</a><br><br>If the project would like to see a more rec=
ent version of geda-gaf go into Fedora (or any other distro that welcomes b=
leeding edge), someone will have to step up and do the packaging.=C2=A0 Fro=
m my past experience with other packages, Fedora will welcome the effort.<b=
r><br>Mitch.<br></div></div>
--089e01493fa82b98a7051fc99379--
- Raw text -