moving uid-gid.txt to metadata

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

moving uid-gid.txt to metadata

William Hubbs
All,

as I recall I was one of the folks who suggested that uid-gid.txt should
go in the api repository, but after thinking about it more and seeing it
in practice, I see the error of my ways on this. ;-)

Imo a better fit is the metadata directory in the ebuild repository.
That way you can add users/groups along with the acct-* packages that
install them.

Thoughts?

William

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: moving uid-gid.txt to metadata

Ulrich Mueller-2
>>>>> On Mon, 20 Jan 2020, William Hubbs wrote:

> as I recall I was one of the folks who suggested that uid-gid.txt should
> go in the api repository, but after thinking about it more and seeing it
> in practice, I see the error of my ways on this. ;-)

> Imo a better fit is the metadata directory in the ebuild repository.
> That way you can add users/groups along with the acct-* packages that
> install them.

> Thoughts?

One (maybe not very strong) argument was that uid-gid.txt also documents
historical assignments, which doesn't belong in the tree.

Ulrich

signature.asc (517 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: moving uid-gid.txt to metadata

Michael Orlitzky
In reply to this post by William Hubbs
On 1/20/20 11:57 AM, William Hubbs wrote:
>
> Imo a better fit is the metadata directory in the ebuild repository.
> That way you can add users/groups along with the acct-* packages that
> install them.
What benefit is there to syncing that file to everyone's machines?

Reply | Threaded
Open this post in threaded view
|

Re: moving uid-gid.txt to metadata

Joonas Niilola
In reply to this post by William Hubbs

On 1/20/20 6:57 PM, William Hubbs wrote:
> All,
>
> as I recall I was one of the folks who suggested that uid-gid.txt should
> go in the api repository, but after thinking about it more and seeing it
> in practice, I see the error of my ways on this. ;-)

What's wrong with it?


>
> Imo a better fit is the metadata directory in the ebuild repository.
> That way you can add users/groups along with the acct-* packages that
> install them.
>
> Thoughts?
>
> William

I think it'd be too easy to 'queue' up work, then ignore conflicts with
UID+GID but push your accts anyway. That's the only downside I came up
with, I don't really mind either way where it is.


-- juippis



signature.asc (655 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: moving uid-gid.txt to metadata

William Hubbs
In reply to this post by Michael Orlitzky
On Mon, Jan 20, 2020 at 12:56:48PM -0500, Michael Orlitzky wrote:
> On 1/20/20 11:57 AM, William Hubbs wrote:
> >
> > Imo a better fit is the metadata directory in the ebuild repository.
> > That way you can add users/groups along with the acct-* packages that
> > install them.
> What benefit is there to syncing that file to everyone's machines?

I don't see this as a concern because the size of the file is
negligible compared to the tree.

William


signature.asc (201 bytes) Download Attachment