Re: [Slackbuilds-users] users and groups
> First, let's assume that "appsomething" needs an "appsomething" > user and group at build time. > > The only way to successfully build it is to create the user and > group prior to the build process. The resulting package, in that > case, will have directories and/or files owned by the "appsomething" > user and/or group, AND/OR some executable in the resulting package > will run as "appsomething" user or group and/or drop privileges > to that user/group after executing, or something alone those lines. > > The above is essentially why we require the user/group to be > in place before running the build script. > > We are aware that in many cases, the initial assumption is not > true - perhaps there are no "appsomething" user/group owned files > in the resulting package, and there's technically no reason to > require the user/group during build time. That's fine, but there's > no harm in creating it. Either way, you now have a package of > "appsomething" that you can install on the build machine, or if > you're like many users, you can copy is to a package storage and > install it on one or more other machines. For those other machines, > the advice to make sure the user/group is present before installation > is correct - for exactly the reason mentioned above about the > possibility of "appsomething" owned directories/files in the package. > > -RW This covers all of my questions and concerns! Thank you very much Mr. Workman and happy new year to everybody. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] users and groups
On Fri, 27 Dec 2019 19:36:41 + Marcelo Caballero via SlackBuilds-users wrote: > All of the SlackBuilds that required to have a user and group they > implement a restriction that prevents the script to continue if the > user or group is missing. I searched the FAQ and the wiki but I was > unavailable to find anything related about this. > > For example from the avahi readme: "First, be sure you have an > "avahi" user and group. Do this *before* you install the avahi > package." So that means that we can run the SlackBuild without a user > and group and then before we install the package we can add the user > and group. But the SlackBuild will fail without user/group... > > This prevents one to build the package in a different machine > (without to worry about users and groups) and then transfer the > package and install it to the preferred machine. Also any custom > script or tool for building packages it would fail without to > modified the SlackBuild first and remove the user and group > restriction. First, let's assume that "appsomething" needs an "appsomething" user and group at build time. The only way to successfully build it is to create the user and group prior to the build process. The resulting package, in that case, will have directories and/or files owned by the "appsomething" user and/or group, AND/OR some executable in the resulting package will run as "appsomething" user or group and/or drop privileges to that user/group after executing, or something alone those lines. The above is essentially why we require the user/group to be in place *before* running the build script. We are aware that in many cases, the initial assumption is not true - perhaps there are no "appsomething" user/group owned files in the resulting package, and there's technically no reason to require the user/group during build time. That's fine, but there's no harm in creating it. Either way, you now have a package of "appsomething" that you can install on the build machine, or if you're like many users, you can copy is to a package storage and install it on one or more other machines. For those other machines, the advice to make sure the user/group is present before installation is correct - for exactly the reason mentioned above about the possibility of "appsomething" owned directories/files in the package. -RW pgpXle8QFjcxI.pgp Description: OpenPGP digital signature ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] users and groups
Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, December 27, 2019 4:02 PM, Marcelo Caballero wrote: > ‐‐‐ Original Message ‐‐‐ > On Friday, December 27, 2019 1:29 PM, Andrzej Telszewski > atelszew...@gmail.com wrote: > > > On 27/12/2019 20:36, Marcelo Caballero via SlackBuilds-users wrote: > > > > > Hello, > > > All of the SlackBuilds that required to have a user and group they > > > implement a restriction that prevents the script to continue if the user > > > or group is missing. > > > I searched the FAQ and the wiki but I was unavailable to find anything > > > related about this. > > > For example from the avahi readme: "First, be sure you have an "avahi" > > > user and group. Do this before you install the avahi package." > > > So that means that we can run the SlackBuild without a user and group > > > and then before we install the package we can add the user and group. > > > But the SlackBuild will fail without user/group... > > > This prevents one to build the package in a different machine (without > > > to worry about users and groups) and then transfer the package and > > > install it to the preferred machine. > > > Also any custom script or tool for building packages it would fail > > > without to modified the SlackBuild first and remove the user and group > > > restriction. > > > Regards Marcelo > > > > Hi Marcelo, > > But even if you remove the restriction on the need to have the > > user/group present, you will encounter another problem. > > That is, package creation will fail during the moment the SlackBuild > > wants to adjusts some paths (dirs, files) to be owned by the particular > > user/group. > > > > Best regards / Pozdrawiam, > > Andrzej Telszewski ‐‐‐ Original Message ‐‐‐ On Friday, December 27, 2019 1:29 PM, Andrzej Telszewski wrote: > On 27/12/2019 20:36, Marcelo Caballero via SlackBuilds-users wrote: > > > Hello, > > All of the SlackBuilds that required to have a user and group they > > implement a restriction that prevents the script to continue if the user > > or group is missing. > > I searched the FAQ and the wiki but I was unavailable to find anything > > related about this. > > For example from the avahi readme: "First, be sure you have an "avahi" > > user and group. Do this before you install the avahi package." > > So that means that we can run the SlackBuild without a user and group > > and then before we install the package we can add the user and group. > > But the SlackBuild will fail without user/group... > > This prevents one to build the package in a different machine (without > > to worry about users and groups) and then transfer the package and > > install it to the preferred machine. > > Also any custom script or tool for building packages it would fail > > without to modified the SlackBuild first and remove the user and group > > restriction. > > Regards Marcelo > > Hi Marcelo, > > But even if you remove the restriction on the need to have the > user/group present, you will encounter another problem. > > That is, package creation will fail during the moment the SlackBuild > wants to adjusts some paths (dirs, files) to be owned by the particular > user/group. > > > > Best regards / Pozdrawiam, > Andrzej Telszewski Hi Andrzej, I removed the user/group from the SlackBuild and I was able to build avahi successfully... ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] users and groups
On 27/12/2019 20:36, Marcelo Caballero via SlackBuilds-users wrote: Hello, All of the SlackBuilds that required to have a user and group they implement a restriction that prevents the script to continue if the user or group is missing. I searched the FAQ and the wiki but I was unavailable to find anything related about this. For example from the avahi readme: "First, be sure you have an "avahi" user and group. Do this *before* you install the avahi package." So that means that we can run the SlackBuild without a user and group and then before we install the package we can add the user and group. But the SlackBuild will fail without user/group... This prevents one to build the package in a different machine (without to worry about users and groups) and then transfer the package and install it to the preferred machine. Also any custom script or tool for building packages it would fail without to modified the SlackBuild first and remove the user and group restriction. Regards Marcelo Hi Marcelo, But even if you remove the restriction on the need to have the user/group present, you will encounter another problem. That is, package creation will fail during the moment the SlackBuild wants to adjusts some paths (dirs, files) to be owned by the particular user/group. -- Best regards / Pozdrawiam, Andrzej Telszewski ___ SlackBuilds-users mailing list SlackBuilds-users@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] users and groups
Hello, All of the SlackBuilds that required to have a user and group they implement a restriction that prevents the script to continue if the user or group is missing. I searched the FAQ and the wiki but I was unavailable to find anything related about this. For example from the avahi readme: "First, be sure you have an "avahi" user and group. Do this *before* you install the avahi package." So that means that we can run the SlackBuild without a user and group and then before we install the package we can add the user and group. But the SlackBuild will fail without user/group... This prevents one to build the package in a different machine (without to worry about users and groups) and then transfer the package and install it to the preferred machine. Also any custom script or tool for building packages it would fail without to modified the SlackBuild first and remove the user and group restriction. Regards Marcelo___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
