Salix Forums

HalfNote5 wrote:The thing is - if you're familiar with a lot of packages (as I am), but not with the particulars of how they're capitalized in SalixOS (as I am not,) it seems like an inconvenience to have to look it up for every package, and remember what is capitalized in which package. Ergo, if there's a way to make slapt-get IGNORE that.....

See my answer:

thenktor wrote:Usually the packages have the exact same name as the source archive they are built from and that's fine. No random renaming.

PS (troll mode on): The random renaming of packages is one of the things I really like. Of course it is obvious that the package is called jackd instead of jack Also I think it's cool to split a package in 1000 sub packages with suffixes like -base, -dev, -bling & -blong

I don't see where you got all those package names in Salix and I don't see how that command should have worked.

Heheh; Obvious typos such as "audactiy" aside (I hate typing from my phone,) it was just an example - and in fact, it didn't work.

Which is why I asked my initial question. I finally got MPlayer to install, and I realized then that capitalization is important in Salix/Slack. (Something I was unaware of until then). What I was hoping for was not to have to bother with it (otherwise, I'd be using the GUI package manager, which is a MUCH easier way to individually look up a bunch of package names - especially if you're trying to install Apache2, and find that Salix uses Cherokee).


Also, I apologise: yes, it is alsa-utils. I was at a client's office and thinking "madwifi-tools" while typing alsa-utils. Which, although being entirely beside the point, DOES makes for a distraction in the example, and easily diverts attention from the topic at hand. Sorry for confusing you.


thenktor: I DO think I'm really going to like having everything put together in one package instead of xyz xyz-utils xyz-dev xyz-tools and all that. It seems a much simpler and more elegant way of doing it.

Also:

That's because the folks at debian never use capital letters in package names.

PRECISELY! It's what I was used to, and it's nice not to have to remember the proper case when you're in an SSH session and trying to apt-get install 20 packages at once, but I can definitely learn to live with it. I'm just kinda getting used to Salix, still, and initially wasn't sure if the naming convention was a result of slapt-get's code, or if that's just the way it is in Salix/Slack.

You've answered my questions beautifully, and I thank you all.

thenktor:

Just wanted to say "thanks" again. Until you mentioned it, I was unaware that Salix/Slack DIDN'T do xyz-dev xyz-base xyz-foo xyz-bar style sub-packages.

Now that I'm aware of this, the whole thing makes more sense and seems MUCH more elegant than I previously thought. (Heheh, and yes, jackd for "jack daemon" isn't exactly what you'd call "obvious" - I guess you just get used to the system you work with.)

Thanks again, everyone. = )

HalfNote5 wrote:especially if you're trying to install Apache2, and find that Salix uses Cherokee

Where did you get that idea? Yes, cherokee is also available, but apache is available too. The package is named "httpd". A "slapt-get --search apache" would have shown you that. Before you ask why the package is named "httpd" instead of "apache", it's because it's developers are naming their source tarballs that way (same case as with MPlayer).

gapan:

Because I found the "cherokee" pkg and not the "apache2" pkg Well, that, and and slapt-get --search apache2 brings up nada. My mistake (I do understand the Salix convention now, and also now understand you can slapt-get --search on a partial name.

At any rate, you'll find it amusing that it occurs to me I could have saved us all a lot of trouble by phrasing my initial query differently. It could have gone something like:

<me> When the man page for slapt-get says "Slapt-get tries to emulate the features of Debian's apt-get as closely as possible." it doesn't really refer to package names and naming conventions, does it?

<you> No.

<me> Gotcha! Thanks!

Again, sorry for confusing you. Now that I understand the answer to my question, and understand slapt-get's DIFFERENCES from apt, based on Salix/Slack being the underlying OS, I can see where I should have presented it differently, and where my assumptions of what "as closely as possible" means were probably my biggest obstacle.


Cheers!

EDIT:

And again, thank you very much.

HalfNote5 wrote:Heheh, and yes, jackd for "jack daemon" isn't exactly what you'd call "obvious"

Actually the "d" is added for no reason. The project is called JACK, the source archive is called jack. I don't know why I would add "d" only because the package contains a daemon. If I would do this with every package, that also contains a daemon it would end up in an mess postfixd, sendmaild, prosodyd, ...

HalfNote5 wrote:Because I found the "cherokee" pkg and not the "apache2" pkg Well, that, and and slapt-get --search apache2 brings up nada.

I guess you just need to get used to less exact search phrases. A search for "apache" does not show to much results because we don't have all these sub packages

HalfNote5 wrote:I guess you just get used to the system you work with.

That's right