From: John B <joh...@gm...> - 2006-04-25 16:16:29
|
We do need a pasture directory. Since I'll be doing primary work on maintaining the repo, I want to have a place to move the old stuff so that it doesn't show up in slapt-get/gslapt, espcially when we've updated core packages due to security fixes, etc. We have to avoid duplicate versions and/or duplicate packages. I can also argue for an unsupported directory, in that it's a place where we put software that is no longer being supported by its author, etc. While we're talking about packaging standards, we absolutely need to use dependencies that are part of the core unless there is a compelling reason to use a different version. I speak mainly of gtk, though this would also apply to qt, wxwidgets, etc. I don't want to see us have multiple versions of gtk2 or qt in the main package tree. One additional comment on the "current" directory - we should take the same position that Patrick V takes with the slackware-current tree. Besides Joe's comment about updated versions of apps and libs being in there (i.e., feature enhancements), it should also be seen as the place where development work on future versions of VL takes place. Therefore, while the stuff in there should work, we should make a strong disclaimer that anything in veclinux-current may break your box. I envision "current" as a directory that would eventually become frozen to a specific release. FWIW, John On 4/25/06, uel archuletta <ue...@gm...> wrote: > I agree with everything, But I read it a little diferently so I would > propose these changes > > > -testing: every package should go here till deemed worthy by a team of > official package testers, then sent to it's rightful place. > > -stable: (or official): only for the specific versions of apps/libs in th= e > release or their security/bug fixes > > > -extra: (or unofficial): for libs / apps not included in the distro. > > -current: for updated versions of libs / apps included in the distro, > but not simple security /bug fixes, rather feature updates. > > -unstable: for beta and rc apps. > > I would also volunteer for testing packages as I have room to keep a clea= n > box to install them onto. > > Thanks > Uel > > > > > On 4/25/06, Jose J. Rodriguez <jo...@gm...> wrote: > > I'd like to awaken this thread because we need to come to a decision > > regarding the structure of the VL6 repo. VL6 will be breaking new > > ground for us in the packaging department, as all packages that make > > up the distro will be available on the repo, to allow for rolling back > > upgrades, etc. Also, we intend to make dist-upgrade possible, as > > discussed before. So we need to get the repo structure just right. > > Also, we need to think about separating the repos for Standard and > > SOHO, or (probably impossible) making the packages installable for > > both. Looking at previous posts, I'd like to sum up a possible repo > > structure and ask for comments/discussions. > > > > -testing: every package should go here till deemed worthy by a team of > > official package testers, then sent to it's rightful place. > > > > -stable: (or official): for bug fixes or security updates of the libs > > / apps included on the distro. > > > > -extra: (or unofficial): for libs / apps not included in the distro. > > > > -current: for updated versions of libs / apps included in the distro, > > but not simple security /bug fixes, rather feature updates. > > > > -unstable: for beta and rc apps, whether included in the distro or not. > > > > -pasture and unsupported have been proposed, but so far I don't see > > the use for them within the timeline of a VL version, your views on > > this? > > > > Regards, > > Joe1962 > > > > > > ------------------------------------------------------- > > Using Tomcat but need to do more? Need to support web services, securit= y? > > Get stuff done quickly with pre-integrated technology to make your job > easier > > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron= imo > > > http://sel.as-us.falkag.net/sel?cmdlnk&kid=120709&bid&3057&dat=121642 > > _______________________________________________ > > Vectorlinux-devel mailing list > > Vec...@li... > > > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > > > > |