LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [ANN] slackdeps (https://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-slackdeps-4175636135/)

ivandi 08-10-2018 10:52 PM

[ANN] slackdeps
 
1 Attachment(s)
With slackdeps you can:
  • create a slapt-get compatible Slackware repository.
  • check the installation for missing libs
  • generate slackpkg templates
  • generate tagfiles for custom install
  • customize the installer with different install options (minimal, server, LAMP ...)
Right now I don't have time to write documentation, but if you have questions I'll try to give more details.

You can try the netinstall.iso.


Cheers

NoStressHQ 08-12-2018 02:27 AM

Looks interesting. Thanks Ivandi.

I'll try to have a look to it.

Cheers.

ivandi 09-02-2018 07:20 PM

The latest netinstall.iso provides three install options minimal, server an desktop. The desktop option installs a XFCE desktop with one GUI application per task and has enough tools to compile some stuff from SBo like galculator leafpad xfburn xfce4-xkb-plugin xarchiver thunar-archive-plugin and libreoffice(repackaged). If you want a super customized setup the menu option is there for you.


Cheers

Darth Vader 09-04-2018 10:24 AM

Quote:

Originally Posted by ivandi (Post 5899177)
The latest netinstall.iso provides three install options minimal, server an desktop. The desktop option installs a XFCE desktop with one GUI application per task and has enough tools to compile some stuff from SBo like galculator leafpad xfburn xfce4-xkb-plugin xarchiver thunar-archive-plugin and libreoffice(repackaged). If you want a super customized setup the menu option is there for you.


Cheers

I believe that will be exceptionally useful to offer another install option: "template"

Like the name suggest, it can offer the ability to specify a custom "template" file. With a remote file support will be even better. ;)

Why? Because I believe that your templates format is much much much more human manageable than the tag files (even in the end they are parsed and transformed to).

No offense for the resident Gurus, BUT even maybe the tag files are really useful as machine readable files, they terrible inefficient way for editing them by humans[1].

[1]Unless those humans are 80 years young men, with really plenty of time at their hands.

ivandi 09-04-2018 11:38 AM

Quote:

Originally Posted by Darth Vader (Post 5899778)
I believe that will be exceptionally useful to offer another install option: "template"

I was thinking about using the custom option for this. I've never used tagfiles with "valid MS-DOS format file extension consisting of a period followed by three characters" ;)


Cheers

Darth Vader 09-04-2018 11:51 AM

Quote:

Originally Posted by ivandi (Post 5899799)
I was thinking about using the custom option for this.

Thank you! I look forward for this feature. :thumbsup:

ivandi 09-05-2018 09:07 PM

Well, it's done. I removed the server and desktop options and modified the custom option.

Now the custom option will ask for an url or path of the template to use. To save typing the testing iso is preconfigured with
http://mirrors.kernel.org/slackware/...are64-current/
and a custom server template from this project
http://www.bisdesign.ca/ivandi/slack...erver.template

I think that a hardcoded minimal.template is still useful. It is not hard to maintain it. The packages in that template are unlikely to be removed or dependencies to change. There is no need to maintain tagfiles as they are generated on the fly.


Cheers

bormant 10-17-2018 04:43 PM

Quote:

The packages in that template are unlikely to be removed or dependencies to change.
Sorry, can not see this template right now, but some time ago 14.2 wget got new library dep (not new to Slackware tree itself), and than minimal install flipped to like pkunzip.zip with no chance to
slackpkg {install,download} anything...
So maintain is needed not on every update, but on every rebuild of any package from the set... If not --
slackpkg upgrade-all
will bring your system to pkunzip.zip state.

ivandi 10-18-2018 06:33 PM

Quote:

Originally Posted by bormant (Post 5916032)
Sorry, can not see this template right now, but some time ago 14.2 wget got new library dep (not new to Slackware tree itself), and than minimal install flipped to like pkunzip.zip with no chance to
slackpkg {install,download} anything...
So maintain is needed not on every update, but on every rebuild of any package from the set... If not --
slackpkg upgrade-all
will bring your system to pkunzip.zip state.

Well, Slackware idiosyncrasies were "cool" back in the day, but nowadays they become a burden.

Anyway, the stuff here generates a slapt-get compatible PACKAGES.TXT. My local Slackware64-current mirror is dependency aware. So when I upgrade wget the new dependency is pulled in.


But one can always use a full blown Plasma5 setup as a LAMP and get on the right side of Bob :D



Cheers


All times are GMT -5. The time now is 04:08 PM.