[Slackbuilds-users] Howto for slackware tgz

[Christoph Willing]

On 13/1/22 11:39, Beco via SlackBuilds-users wrote:
> Hi Jeremy, hi Chris,
> 
> Thanks for the tips, guys.
> 
> I'll take a look at every link.
> 
> Currently I'm having trouble with my printer, Epson M105, and I'm
> trying to adapt source code from drivers I've found in "src.rpm" to
> slackware package format.
> 

Have a look at:
	https://slackbuilds.org/repository/14.2/system/epson-printer-utility/

whose README.models claims to support the M105 Series (and is based on
a src.rpm too).


chris


> Maybe I should start with something simpler, even though I'm an
> experienced linuxer from a long time, each distro has its own
> challenges.
> 
> Best regards,
> Bèco
> 
> 
> On Wed, 12 Jan 2022 at 10:42, Chris Abela <kristofru at gmail.com> wrote:
>>
>> See here:
>>
>> https://www.slackwiki.com/Packages
>> https://www.slackwiki.com/Building_A_Package
>> http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
>> http://docs.slackware.com/howtos:find_packages_with_filenames
>> http://docs.slackware.com/howtos:slackware_admin:querying_installed_packages
>>
>> You will find that as Slackware does not track dependencies, it is resilient to most hacking possibilities.
>>
>> As a tutorial, try to build a helloworld package.
>>
>> On Tue, Jan 11, 2022 at 4:29 AM Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>>>
>>>
>>>
>>> On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>>>
>>>> Hello there, Slack users,
>>>>
>>>> I just joined.
>>>> I hope you are all doing well, and that this list is still active.
>>>>
>>>> I am migrating from Debian systemD. I tried Devuan as well. It is
>>>> difficult to change distros when you have many computers/notebooks and
>>>> you want them to share the same distro.
>>>>
>>>> Some of my small scripts and programs need to adapt. It is not a big
>>>> deal, but I want them to keep organized. I think the best way is to
>>>> reorganize them within the parameters and directory structure of a
>>>> slackware package.
>>>>
>>>>
>>>> Please, what is a good updated detailed source of explanation about
>>>> the format and internals of a tgz tar-ball (package)?
>>>>
>>>>
>>>> Thanks and still in time, happy 2022.
>>>
>>>
>>>
>>> Welcome! They're pretty simple. The majority of it is simply extracted to the root filesystem and is stored with the exact layout it is expected to have on the root filesystem.
>>>
>>> Where it differs is the install/ directory. This houses the files for the Slackware package manager. The two most common are slack-desc and doinst.sh. The former is used as the information displayed by Slackware's package manager during installation and maintenance. The latter is an optional file that is run immediately after the package is installed. You can see SBo's templates for both at the below address.
>>>
>>> Good luck,
>>> Jeremy
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
>>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> 
>