> Software shouldn't really rely on files being owned/writable by certain
users.
Sure, software shouldn't rely on files being owned/writable by *certain*
users. But it's reasonable for software to rely on files being
owned/writable by *a* user. Consider, for example, `mpd` and `subsonic`.
Both pro
Am 25.01.2014 17:13, schrieb Maxime Gauduin:
> The reason why permissions should be set in the PKGBUILD is because that
> way pacman can track them. Then it's up to the maintainer to choose
> UIDs/GIDs that do not conflict with official packages, and to the user to
> check that they don't already u
You might wanna have a look at this: https://bugs.archlinux.org/task/36770
Yeah, but there's less packages in core/community than in AUR. Arch
Linux Developers and TUs can agree on some UIDs and GUIDs so packages
don't conflict. In AUR you can't. ;-) That's why I said "AUR
guidelines", not
On Tue, Feb 4, 2014 at 3:35 PM, Nowaker wrote:
> I've rewritten the inspircd package so that file ownership is assigned in
>> the .install file.
>>
>
> Thanks for reviving the thread. :) I too think useradd and groupadd in
> .install is the way to go, as I said in the first post. This has always
I've rewritten the inspircd package so that file ownership is assigned in
the .install file.
Thanks for reviving the thread. :) I too think useradd and groupadd in
.install is the way to go, as I said in the first post. This has always
worked for my packages well. Just inspircd, an adopted pac
> * One can perform system-independent actions in the PKGBUILD functions.
> This includes dictating where files should be installed.
> * One can perform system-dependent actions in the .install functions. This
> includes assigning an owner to a file (and, therefore, touching user IDs).
>
> I've rew
>>> As for a better solution? Hmm. `install` (and probably other tools too)
can reference user and group names directly. [...]
>> The problem with that is that the uid/gid for the permissions will be
computed on the machine where the package is built, [...]
> It won't work for packages from AUR eit
On Mon, Jan 27, 2014 at 6:53 PM, Nowaker wrote:
> You forgot to attach the script or ML stripped it.
Oops! I'll try attaching it again, if the ML strips it I'll just inline it.
As for a better solution? Hmm. `install` (and probably other tools too) can
reference user and group names directly. Thus, this:
The problem with that is that the uid/gid for the permissions will be
computed on the machine where the package is built, and there is no
guarantee that the same uid/
On Mon, Jan 27, 2014 at 2:44 PM, Emil Lundberg wrote:
> Of course this isn't a problem if the package is only in the AUR, but
> it eliminates the option to prebuild the package (for inclusion in the
> official repositories, for instance).
Sorry for double posting, it struck me right after sending
On Mon, Jan 27, 2014 at 5:35 AM, Jeremy Audet wrote:
> As for a better solution? Hmm. `install` (and probably other tools too) can
> reference user and group names directly. Thus, this:
>
>> install -o141 -g141 -dm750 "${pkgdir}/var/log/inspircd"
>
> Could also be written as this:
>
>> install -o
> The reason why permissions should be set in the PKGBUILD is because that
> way pacman can track them.
Interesting. I didn't know Pacman could do that. The phrases "UID", "uid"
and "gid" do not appear in the man pages for pacman or pkgbuild. Is this
undocumented behaviour?
> Then it's up to the
Maxime Gauduin wrote:
>The reason why permissions should be set in the PKGBUILD is because that
>way pacman can track them. Then it's up to the maintainer to choose
>UIDs/GIDs that do not conflict with official packages, and to the user to
>check that they don't already use that particular UID/GID
On Sat, Jan 25, 2014 at 4:03 PM, Nowaker wrote:
> Hey,
>
> What is the prefered way of creating users/groups and handling files
> ownership for AUR packages?
>
> My take is to change the file ownership (`chown`) in .install script.
> That's what I do in the PKGBUILDs I write myself.
>
> However,
Hey,
What is the prefered way of creating users/groups and handling files
ownership for AUR packages?
My take is to change the file ownership (`chown`) in .install script.
That's what I do in the PKGBUILDs I write myself.
However, inspircd, which I adopted a few months ago takes a different
15 matches
Mail list logo
