Im agreed with Jesse ... we must expose the devel and qa images. and explain isos objectives (:2-qa its for test and why) and (:2-devel for development) then put more info of why not release stable ... packagekit update-system memory consumation etc,etc .....
If i end user i would like to know why my distro its not updated and not release as new. On Fri, Jul 2, 2010 at 10:37 AM, Andres Vargas <zod...@foresightlinux.org>wrote: > Hi richard of course we can .. :> for info asap on IRC plz. welcome to > foresight packaging. > > The next time create a new thread for package problems on mail-list > > > > > On Fri, Jul 2, 2010 at 10:08 AM, richard kim <r...@rattaroaz.com> wrote: > >> Hi everyone. If I can make a request, after releasing the next version of >> foresightlinux, would someone be willing to do a "teach how to package >> with >> conary" session? I tried to go through the documents, but I can't figure >> it >> out. It seems to jump around, it is hard to follow, and nothing I do >> seems >> to work. (I'm not that smart either). I would be willing to rewrite some >> of it as needed, and even do a video tutorial if I can figure it out. I >> just need to be able to figure it out first. This might be a good way to >> kick off the rebirth of foresight as well. Thanks. >> >> Richard >> >> On Fri, Jul 2, 2010 at 1:50 AM, Zhang Sen <zh.je...@gmail.com> wrote: >> >> > Hi list, >> > >> > As everybody knows, there are not many new users coming at this >> > moment. But sometimes we do see new users, such as >> > http://forum.foresightlinux.org/index.php?topic=867.0. And the most >> > frequent scenario that happens is like this: >> > >> > Q: Is foresight still alive? >> > A: Yes. But only for devel/qa branches. >> > Q: OK. But I met a problem (example: and >> > http://forum.foresightlinux.org/index.php?topic=869.0). >> > A: You need to install the foo and bar packages from the qa branch. >> > Q: ... (system is messed up) >> > >> > What I have been thinking is that, having the 2.1.x releases available >> > is actually hurting us. It presents a false impression about foresight >> > to the new users. Users got a broken system (esp. about hardware >> > support); and there is no way we can fix the problem for the user; and >> > user thinks foresight packages are all old and one needs various >> > tweaks to make it work. >> > >> > What I propose is that, we pull the old releases down from the >> > website, and put the qa images there, along with a warning that >> > "Foresight is still alive, but there is no releases recently. If you >> > want to have a try, use the qa images at your own risk." >> > >> > Jesse >> > _______________________________________________ >> > Foresight-devel mailing list >> > Foresight-devel@lists.rpath.org >> > http://lists.rpath.org/mailman/listinfo/foresight-devel >> > >> _______________________________________________ >> Foresight-devel mailing list >> Foresight-devel@lists.rpath.org >> http://lists.rpath.org/mailman/listinfo/foresight-devel >> > > _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
