[Slackbuilds-users] users and groups

[Marcelo Caballero]

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, December 27, 2019 4:02 PM, Marcelo Caballero <Marcelo.Caballero at protonmail.com> wrote:

> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, December 27, 2019 1:29 PM, Andrzej Telszewski atelszewski at 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 <atelszewski at 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


Hi Andrzej,

I removed the user/group from the SlackBuild and I was able to build avahi successfully...