vectorlinux-devel

[Vectorlinux-devel] /etc/vector-version

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

Good morning!

With the proliferation of different versions of VL (live, SOHO, standard,
deluxe and permutations thereof), I would like to request that the
/etc/vector-version file clearly state the version as specifically as
possible. For example, if the release is VL standard 5.1 Live RC2, we could
state VectorLinux 5.1 LiveRC2 as the version. For a SOHO release, we should
state something like this: VectorLinux 5.1 SOHO Live3 or VectorLinux 5.1SOH=
O
. Finally, for a Deluxe version we should state the version as VectorLinux
5.1 SOHO Deluxe.

The reason I am bringing this up is that helping new users will be easier i=
f
we can tell them to type cat /etc/vector-version in a terminal and have the=
m
post the result in the forum, rather than telling them to just "guess" at
what they downloaded. Truth be told, some users aren't sure whether they
downloaded VL or not. This particular thread from the forum is a great
example of why this e-mail:
http://www.vectorlinux.com/forum/viewtopic.php?p=3D58502#58502

The OP in that thread claims to be using VL Deluxe, yet the symptoms he's
posting don't necessarily reflect that, unless he's using a deluxe version
of 5.1 standard.


Thanks for your consideration,
John

Re: [Vectorlinux-devel] /etc/vector-version

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

On 3/12/06, John B <joh...@gm...> wrote:
> Good morning!
>
> With the proliferation of different versions of VL (live, SOHO, standard,
> deluxe and permutations thereof), I would like to request that the
> /etc/vector-version file clearly state the version as specifically as
> possible. For example, if the release is VL standard 5.1 Live RC2, we cou=
ld
> state VectorLinux 5.1 LiveRC2 as the version. For a SOHO release, we shou=
ld
> state something like this: VectorLinux 5.1 SOHO Live3 or VectorLinux 5.1
> SOHO . Finally, for a Deluxe version we should state the version as
> VectorLinux 5.1 SOHO Deluxe.


I discussed a related issue a while back with some of you (sorry, bad
memory, lol), regarding a way to implement version-related package
dependency. By this I mean that a package has a dep on SOHO 5.1, for
example, and will not install on SOHO 5.0, etc. The solution proposed
at the time, IIRC, was a dummy package with the VL version, which
could be used as a dep inside the app packages.

A problem remaining with this is that some packages should install to
both Standard and SOHO versions, while others might not be designed
that way. If the neccesary SOHO packages are deps of the package, then
it should pull them into Standard and work, but sometimes Standard has
some basic differences with the corresponding SOHO that might defeat
this. Solutions to this that come to mind are: 1) Establishing
separate package repos for Std and SOHO, 2) working from the "base" VL
we've been discussing for 6.0 and not changing anything critical that
comes from it before release of both Std and SOHO.

Regards,
Joe1962