vectorlinux-devel — Vector Linux developer's list

Re: [Vectorlinux-devel] "Unstable" repository

[Tony B. <tb...@gm...>]

I started work on a repackaging tool just before I left.  It took the
entries from /var/log/packages and /var/log/scripts and repackaged them as =
a
tgz package.  IMHO, this would be the best way to create individual package=
s
after tweaking and then also create some custom vl packages to encompass
/etc/skel and /root.

we really need to start creating new folders for each version.  We are usin=
g
5.0 on the repo and the version of the distro is 5.1.  This is confusing an=
d
needs to be addressed before the next version.



On 3/2/06, John B <joh...@gm...> wrote:
>
> To add to Tony's comments, we should also add pasture and unsupported
> subdirectories in the main repository. They would serve the same purpose
> that they do in Slackware - pasture would be used for holding old package=
s,
> and unsupported would be the holding place for packages we no longer supp=
ort
> but should be kept around for historical interest.
>
> While we're talking about the repository, I think we should enable the
> ability to use the slapt-get --dist-upgrade flag to enable upgrade to a n=
ew
> version without having to download and install an ISO. If we do this,
> however, it would mean that we would have to have EVERY package that woul=
d
> come on an ISO in our repository, especially for the benefit of the VL us=
ers
> who don't want to enable the official slackware repos. Let's hash this ou=
t
> some on the list. If Jason Woodward, aka jaos, has been invited to this
> mailing list, I'm sure he'll add some insight on this.
>
> Regards,
> John
>

Re: [Vectorlinux-devel] "Unstable" repository

[John B <joh...@gm...>]

To add to Tony's comments, we should also add pasture and unsupported
subdirectories in the main repository. They would serve the same purpose
that they do in Slackware - pasture would be used for holding old packages,
and unsupported would be the holding place for packages we no longer suppor=
t
but should be kept around for historical interest.

While we're talking about the repository, I think we should enable the
ability to use the slapt-get --dist-upgrade flag to enable upgrade to a new
version without having to download and install an ISO. If we do this,
however, it would mean that we would have to have EVERY package that would
come on an ISO in our repository, especially for the benefit of the VL user=
s
who don't want to enable the official slackware repos. Let's hash this out
some on the list. If Jason Woodward, aka jaos, has been invited to this
mailing list, I'm sure he'll add some insight on this.

Regards,
John

Re: [Vectorlinux-devel] "Unstable" repository

[Tony B. <tb...@gm...>]

Stable should be reserved for all packages that are either the same version
or a bugfix or securyt fix version of the original app included in the
distribution.

An upgrade to something like KDE 3.5.x should be considered "current" and
not necessarily unstable. This is where development on the next version
should take place like slackware and so many other distros do.  This would
also provide an upgrade path for previous versions and solve that issue as
well as a lot of folks always want to upgrade their system without having t=
o
reinstall the os.

Clearly any app that is in true beta form should be in "unstable" and shoul=
d
remain there until it is not beta anymore.  There are a lot of beta apps
that are really stable and shouldn't be deemed beta anyway.  Latest and
greatest apps should go here and when they pass the muster, they should be
moved to current.

I believe there should also be an "extra" repo where addon apps are put
after the final version of the distro has been released.  Lets say someone
wants avidemux or dydstyler, they should go here and not stable as the
distro never had it to begin with and for the most part it is untested on a
large enough scale.  This would also put less pressure on the maintainers o=
f
the extra repo apps.

This way the people that want a rock solid distro without having to get new
packages or go bleeding edge, could be assured that the stable repo will
only have bugfixes or security fixes for the main distro.

I don't see a point in having a bugfix or security repo as those can just b=
e
seemlessly roled back into the stable repo.

The stable repo would be the most important, followed by the extra repo and
then the current repo.

Regards,
Tony aka Spider



On 3/2/06, Jose J. Rodriguez <jo...@gm...> wrote:
>
> Were not all here yet (we've got around 66% of the proposed members
> in), but sort of to break the ice, here goes my first post to the
> list. And it's sort of the reason behind the list idea, since johnvan
> was already gone for the night and I didn't want to forget about this
> matter, lol. I think a non-realtime discussion vehicle like this is
> also very useful and doesn't require you to be online at the Forum
> either.
>
> As I was packaging Amarok 1.4 beta1 last night, I was wondering if I
> should upload it for general consumption, because it's a beta app and
> people tend to upgrade everything lately, something that has caused
> problems already. So I figured we need an "unstable" repository. We
> have "testing", but that's for testing packages with regard to
> packaging problems. All packages should start in testing, but then get
> moved to "stable" or "unstable" according to the status of the app
> itself.
>
> Regards,
> Joe1962
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid=110944&bid$1720&dat=121642
> _______________________________________________
> Vectorlinux-devel mailing list
> Vec...@li...
> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel
>

[Vectorlinux-devel] "Unstable" repository

[Jose J. R. <jo...@gm...>]

Were not all here yet (we've got around 66% of the proposed members
in), but sort of to break the ice, here goes my first post to the
list. And it's sort of the reason behind the list idea, since johnvan
was already gone for the night and I didn't want to forget about this
matter, lol. I think a non-realtime discussion vehicle like this is
also very useful and doesn't require you to be online at the Forum
either.

As I was packaging Amarok 1.4 beta1 last night, I was wondering if I
should upload it for general consumption, because it's a beta app and
people tend to upgrade everything lately, something that has caused
problems already. So I figured we need an "unstable" repository. We
have "testing", but that's for testing packages with regard to
packaging problems. All packages should start in testing, but then get
moved to "stable" or "unstable" according to the status of the app
itself.

Regards,
Joe1962