Re: [Shr-User] Putting the *S*table back in *S*HR!
On Fri, Aug 28, 2009 at 6:38 PM, Tomt...@stosb.com wrote: [...] The goal will probably be creating and testing a new testing image every 2 weeks or so. Though we haven't officially decided on that. May you elaborate? why every 2 weeks a new testing image? will not creating a single testing image and opkg update opkg upgrade be sufficient? Regards Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] Putting the *S*table back in *S*HR!
Am Samstag 29 August 2009 14:00:29 schrieb Nicola Mfb: On Fri, Aug 28, 2009 at 6:38 PM, Tomt...@stosb.com wrote: [...] The goal will probably be creating and testing a new testing image every 2 weeks or so. Though we haven't officially decided on that. May you elaborate? why every 2 weeks a new testing image? will not creating a single testing image and opkg update opkg upgrade be sufficient? yeah, but for those installing it freshly having to flash and then upgrade is a pain... And the longer the list of packages to update... the more probable it will be that opkg bails out. Regards Nicola -- Klaus 'mrmoku' Kurzmann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Shr-User] Putting the *S*table back in *S*HR!
On Sat, Aug 29, 2009 at 3:25 PM, Klaus 'mrmoku' Kurzmannm...@mnet-online.de wrote: Am Samstag 29 August 2009 14:00:29 schrieb Nicola Mfb: On Fri, Aug 28, 2009 at 6:38 PM, Tomt...@stosb.com wrote: [...] The goal will probably be creating and testing a new testing image every 2 weeks or so. Though we haven't officially decided on that. May you elaborate? why every 2 weeks a new testing image? will not creating a single testing image and opkg update opkg upgrade be sufficient? yeah, but for those installing it freshly having to flash and then upgrade is a pain... And the longer the list of packages to update... the more probable it will be that opkg bails out. Ah! so creating and testing means building ;) Happy to hear that! about opkg why do not use an old version? in the past it worked fine. Regards and keep up the upcoming good work ;) Nicola ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Putting the *S*table back in *S*HR!
hey all, As I (and others) mentioned in the recent OM2009 thread - One of the great advantages of SHR is that it is being developed so quickly. However, I'd also say that one of the great *DIS*advantages of SHR is that it's being developed so quickly that it's often not very stable, and the 'testing' build is woefully out of date. I don't have very much spare time in my life right now, so I unfortunately can't take it on myself, but I think it'd be very beneficial if someone was willing to step up and take charge of getting shr-testing updated periodically, and maybe even releasing an shr-stable that has at least some of the snazzy stuff from shr-u in it. I can help with stability testing, and maybe a bit of documentation, but I can't go much beyond that... Anyone else willing and able to take this on? Warren -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Putting the *S*table back in *S*HR!
Warren Baird ha scritto: hey all, As I (and others) mentioned in the recent OM2009 thread - One of the great advantages of SHR is that it is being developed so quickly. However, I'd also say that one of the great *DIS*advantages of SHR is that it's being developed so quickly that it's often not very stable, and the 'testing' build is woefully out of date. This is why I never used SHR (and I won't for many time to come, I think) I don't have very much spare time in my life right now, so I unfortunately can't take it on myself, but I think it'd be very beneficial if someone was willing to step up and take charge of getting shr-testing updated periodically, and maybe even releasing an shr-stable that has at least some of the snazzy stuff from shr-u in it. Or rename it UHR (Unstable Hybrid Release) :P Bye! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Putting the *S*table back in *S*HR!
2009/8/27 DJDAS dj...@djdas.net Or rename it UHR (Unstable Hybrid Release) :P Bye! The meaning of SHR is pretty much historical by now :-) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Putting the *S*table back in *S*HR!
On Thu, Aug 27, 2009 at 11:39:13AM -0400, Warren Baird wrote: As I (and others) mentioned in the recent OM2009 thread - One of the great advantages of SHR is that it is being developed so quickly. However, I'd also say that one of the great *DIS*advantages of SHR is that it's being developed so quickly that it's often not very stable, and the 'testing' build is woefully out of date. Perhaps mv shr-2009-08-08 shr-testing ? Don't forget the known issue: opkg-cl update ; opkg-cl install opkg ... from now on, opkg bla bla bla again. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
