Re: [GNU-linux-libre] NONFSDG: Audacious plugins, Xchat

[jaromil]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


hi Karl,


> On Mon, 27 Sep 2010 10:10:44 +0200 jaromil <address@hidden> wrote:
> > one solution i see is just provide a .patch for the upstream code
> > and leave distro developers and mantainers apply it every time
> > they make a new release: a minimal, short term solution.

On Wed, Sep 29, 2010 at 08:36:35PM +0930, Karl Goetz wrote:
> Not really. its /the/ solution if upstream doesn't want to accept
> the patch.  One of the big problems with this is different distros
> with different versions of applications trying to use the same
> patches as code evolves.

ACK. so i should include in the steps outlined the first one: propose
the patch to upstream.

is there a page resuming a short "what to do" when trying to liberate
software packages?

> > a long term solution can be that of setting up and mantaining a
> > "buildbot" with public repositories for various distributions, hosting
> > liberated packages that we patch and make available for the
> > public. internally at dyne.org we have such a buildbot to test
>
> I don't really see this as a better solution for distributions then
> the first tbh. For the public? perhaps better. for us? not a whole
> lot.

i see your point here.

> > upstream development of software: builds at every new commit and
> > reports failure on building on various platforms (via mail or
> > irc), ATM we have 32 and 64 bit debian, fedora, gentoo and ubuntu.
>
> I've thought about such things for various projects im involved in,
> but maintaining it and debugging requires much time/effort/skill
> then i have to hand.

of course this is a task for sysadmins with time at hand.  and we know
some. one of such buildbots is mantained by us, but it's on a donated
virtual machine running Xen and the donor cannot support us longer.
it's not difficult to setup, if resources are available.  else we have
to proceed raising our dependance from costly infrastructure and go
hire our own hosting. but you see what i'm saying is that at dyne we
do have the time/effort/skill for setting up such things, just lacking
infrastructure for it, so we could share both.

> mantaining a single buildbot > server/farm (easily setup with
> cowbuilder) can relief a lot of > system administration hassles for
> many of us.
>
> I can see a lot of potential issues, but there are potential gains
> too.
>
> > an ideal partner to host us could be the compile farm for GCC,
> > mantained by Laurent Guerby http://gcc.gnu.org/wiki/CompileFarm
> >
> > excusez-moi pour le rêves de grandeur :)
>
> um...? :)

means "excuse me for the dreams of greatness" :) since this idea of a
buildbot its kind of one one could see it as a "launchpad" for
linux-libre..  ..without having to sign silly contracts and be called
"ubuntero" :) and most importantly based on more distributions, not
just ubuntu, but all those platforms adopted by libre distros here.

ciao


- --
jaromil, dyne.org developer, http://jaromil.dyne.org

GPG: B2D9 9376 BFB2 60B7 601F  5B62 F6D3 FBD9 C2B6 8E39



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQQcBAEBCAAGBQJMpEygAAoJEAslGzkIl3JR3fQf/itmJ2x4dCRpiyOb5fYX6lli
8ZafkVRdqOK2Ombsmy87wlC9hvcupZueOs6fifis5DdHIAV2ddMEYS2LomYVTZuH
CypkVBlti861mnPtAh4AX/X5fD5gbvsnsNaVFxcH81VHRnRIoNGT8u0DbcrX/dRz
YH9IpJ/jG2uhXBcsRDJ5MC6Q53rrI2GtheLTTbvv6I4MVyaN0QJYALHHzTPTL2x2
i9N72AN2WE6aQHZaGy/YqCtkllyEO9EKOl9mIEKbe3KgnRgGuf6JNPUxEyLC02Sn
rGYz05MvRXm270Ddv7DVYZ83XEGEufYmtxxAP7S6lBP6sv2zz3OW0WXrrdwahW5+
2YHsPfz6o0s1YxVWLZGnV0o4iRUOm48E/T/o/PARo/kaQ4PYTEvdvr9fcIuEYDJD
md87jJi+2m5lMV4ZgV9Ja/a+vXE9gqMFYPCDgAbxvf/JWikB7sDuFAVrUCATBa+1
BI4Jw9Sn5+WayLCOmN61R5suKV+80Jjt1cRCALc8TID0lJoGDZQFGvJlpOfvJten
G9Ft9/7jpO32lCt7d0S3u0FEM5q+DNCzC6iieS6fxlEXZdQhmV6vKbKE1Pmvl9mV
cS+34rEmPKF/vtagHJcmqAheQBa60kGYCl/3jhdrRi1gV4QMwfrzmIBzzx7/ySUz
Ix9KymrfW6jtFLUKl4+CLLJwDh3w5dOs7Kb+RFVMXMWTax76NZ6v8h4aWF3ves9+
uBCmL5y5GYNlyaPhiTqQ+emVI0dpPoZGEh/qyBSPsmglzjHGVs4r5mx2YDb4+6aE
PG/zJTn0QIwD1fUMJy0eUdO3Kk7wiRcS+V5EUWky6WB0r/39BSAVnMKAMNt9NwkR
UpgLsv2l3Azdthu6zP1DcyTc1dWaVBhFyveH62MdzEa2KaMiL2BziDfBSrhh8S35
cl7CA0boThExAJ+4EjDWnZr1DpfFQTFxXEjJTRFdL8XOCGJsM4oC35OOoj+HsGb4
MHVcfxAkdQG4bzJv6Rkei8aXirReBHPT94N33A891g5a4RNSwiOskwt8Kyj6/l5r
5YqTxxJk+1d/QK5uj9rLnk+M+OrJ4lrYOi7PS+Bd2Fa3B4wshmWMUxu3KQFre3EE
zvfBg3tiTXJHItvDr9nIlgIBEEUZcsbS/iViEPEJqhLPLFgGT9osyPQUtXZDHtad
/9JJWd53F6zJ8CQtOfXxp5U0CSeJQnGR0/wzBe4QLBzypvjuUpB6xGk0GfDnGUPN
BkRgOL3Fq4+uGPemAIqPuXi7LBblnpnfGgekmWJlc9zJbjaOcnVdPQ+qjFR28cUa
9dmn/zaCIOoXDJefB9wgyfU5ZrpiNnctCET4wTi3f1F1w9GJ9pekQpPnqsEboRk=
=C54m
-----END PGP SIGNATURE-----