Salix OS

I've noticed that our repository current is organized like this:

i486/ISOs/current
i486/packages/current
i486/sources/current

I'am proposing to have it the other way round, like

i486/current/ISOs
i486/current/packages
i486/current/sources

That way, when a new version is out, we only have to do cp -a current $newver, as it is, we need to do it three times.

In package manager:
i486/ISOs/current
i486/packages/current
i486/sources/current

looks better (version information at the end).

a simple script can do the copying:
for XYZ in ISOs packages sources; do
cp - $XYZ/current $XYZ/$newversion
done

But the package manager only cares about the packages part, it's never going to care about the sources and ISOs part. Plus, it's easier to navigate from packages to sources (one up, one down).

I noticed on the repo that the description of some files still refer to Zenwalk...

Also in the under title, it says that 'our' distro is based on Slackware & Zenwalk.

Although most folks here, so far, come from Zenwalk Land, does any substantial code actually come from Zenwalk?

Just curious.

No, I don't think so, not yet at least. Though we could definitely use the systemtools part at least I think.

One more thing the i486/current/packages structure is better: we can create a FILELIST.TXT file (as in slackware). It's easy to see the entire contents of the repository of a given version this way, packages, sources everything. Also that's the way all slackware repos are

Then feel free to change it, no problem for me

I've changed the structure. Created category dirs in the sources dir as well.

thenktor wrote:I've changed the structure. Created category dirs in the sources dir as well.

Good!

We should be a bit careful with the category dirs in the sources dir (although I like the idea a lot): if we move packages to another category in the package repo, they should also be moved in the sources repo. The problem is a lot less annoying here than in Zenwalk because we don't have the iso/extra separation. The source repo in Zenwalk has the same packages all over the place and is really unmaintained.

Hi Akuna

I've done the structure that way because I think like this :
Hey, I want this distro, so ok, what archi I have ? mmm i486 ok. Then, what do I want ? (and ISO, a package repository ?). Then, hum which version ? ok this one.

This was the reason for the order. But I'm ok with the change.

About Zenwalk description for files, it's just that I forget to change it (copied from Zenwalk mirror).
For about the "based on Slackware and Zenwalk" I don't think it is false. We use SLKBUILD which are based on ZENBUILD, and I'm sure we will use others things later. Why reinvent the wheel, and why don't take some good tools (zpm, zendo, zenpanel, ...)