/etc/slackware-version still reports 13.37 after upgrade to -current

[Paul]

A few days ago, I used slackpkg to upgrade to slackware-current from
13.37, which had been installed from CDs. When I `cat
/etc/slackware-version`, it still reports that slackware 13.37 is
installed. Is this correct, given that I'm now running -current?

If not, is it normal for this file to remain untouched by the (from what
I gathered doing Google searches) "normal" way of upgrading the entire
distro using slackpkg (change the
mirror/update-all/install-new/clean-system)?

If this file normally does not get updated by slackpkg, should I
manually update it? In other words, will everything work OK with the
"wrong" version in there?

If I should manually update the contents of /etc/slackware-version, what
*should* it containt for slackware-current?

--
Your lucky number has been disconnected.

[Lew Pitcher]

On Monday 04 June 2012 09:05, in alt.os.linux.slackware,

PaulB...@gmail.com wrote:

> A few days ago, I used slackpkg to upgrade to slackware-current from
> 13.37, which had been installed from CDs. When I `cat
> /etc/slackware-version`, it still reports that slackware 13.37 is
> installed. Is this correct, given that I'm now running -current?

Yes, sort of.

Remember, "current" is Pat's working area, his transition area from the most
recent Slackware release and the /next/ Slackware release. It is not
guaranteed to be stable or consistant (as a release) until PV
actually "releases" it. As "current", it is /not/ a Slackware "release",
but an unreleased "work in progress".

The contents of /etc/slackware-version are maintained by the aaa-base
package, which is one of the last packages that PV updates when he releases
a new version of Slackware. In the current "current" package tree, the
aaa-base package is still the one from the Slackware 13.37 release.

/Until/ that new version is released, the aaa-base package in current
usually contains the slackware-version file from the /previous/ version of
Slackware. And, so, if you "upgrade" your Slackware installation
from "current", you get the slackware-version of the last official release.

HTH
--
Lew Pitcher

[Michael Black]

On Mon, 4 Jun 2012, Paul wrote:

> A few days ago, I used slackpkg to upgrade to slackware-current from
> 13.37, which had been installed from CDs. When I `cat
> /etc/slackware-version`, it still reports that slackware 13.37 is
> installed. Is this correct, given that I'm now running -current?
>

I don't know, but what else would it be? If it was "current" that
wouldn't tell you a thing, it could be a never updated leftover from
the period between Slackware 7.0 and 7.1.

There is no release number issued to current until a new release is about
to come out. Usually the changelog says something like "I guess we'll
call this Slackware 15.5" and there it is. The number has some sense to
it, but there's no schedule to releases so it can't be seen ahead. The
number would depend on what's changed since the last release, if there are
significant changes to the core, then it's a major upgrade, if it's just
ruotine, it's a minor upgrade. That may not be known until things are
ready to release, hence it can't be numbered until then.

Michael

[Paul]

On 2012-06-04, Lew Pitcher <lpit...@teksavvy.com> wrote:
> On Monday 04 June 2012 09:05, in alt.os.linux.slackware,
> PaulB...@gmail.com wrote:

>> A few days ago, I used slackpkg to upgrade to slackware-current from
>> 13.37, which had been installed from CDs. When I `cat
>> /etc/slackware-version`, it still reports that slackware 13.37 is
>> installed. Is this correct, given that I'm now running -current?

> Remember, "current" is Pat's working area, his transition area from the most
> recent Slackware release and the /next/ Slackware release. It is not
> guaranteed to be stable or consistant (as a release) until PV
> actually "releases" it. As "current", it is /not/ a Slackware "release",
> but an unreleased "work in progress".

> The contents of /etc/slackware-version are maintained by the aaa-base
> package, which is one of the last packages that PV updates when he releases
> a new version of Slackware. In the current "current" package tree, the
> aaa-base package is still the one from the Slackware 13.37 release.

> /Until/ that new version is released, the aaa-base package in current
> usually contains the slackware-version file from the /previous/ version of
> Slackware. And, so, if you "upgrade" your Slackware installation
> from "current", you get the slackware-version of the last official release.

OK, that's what I suspected (and hoped) was the case. I just needed some
confirmation that the upgrade hadn't been borked in some way.

Thanks for the explanation.

--
In the first place, God made idiots; this was for practice; then he made
school boards.
-- Mark Twain