[gentoo-dev] RFC: UID/GID assignment for kibana (269)
I would like to reserve UID/GID 269 for kibana (www-apps/kibana-bin). The uid/gid used in Arch for kibana is taken by qmail in Gentoo. Pending PR: https://github.com/gentoo/gentoo/pull/12984 Thanks, Tomas
[gentoo-dev] RFC: UID/GID assignment for elasticsearch (183)
I would like to reserve UID/GID 183 for elasticsearch (app-misc/elasticsearch). It's the same as in Fedora. Pending PR: https://github.com/gentoo/gentoo/pull/12983 Thanks, Tomas
Re: [gentoo-dev] Underscores in USE flags
On Fri, 2019-09-20 at 13:46 -0700, Zac Medico wrote: > On 9/20/19 8:46 AM, Mike Gilbert wrote: > > Recently, a large number of bugs were filed against packages that have > > USE flag names which contain underscores. Apparently PMS prohibits > > this except when the USE flag is part of a USE_EXPAND variable. > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > I'm not certain when this text was added to PMS, or how many of the > > affected USE flags pre-date this policy. > > > > Portage seems to have no issue dealing with underscores, so this > > doesn't seem to be solving any technical problem. > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > amount of end-user confusion, for very little benefit. Is enforcing > > this part of PMS really worth it? > > If we take this underscore rule to its logical extreme, then we should > rename python_targets_python3_7 to python_targets_python3-7, yes? Believe me, I would have done that already if not the fact that with all the dependency logic around here it would be totally destructive to all Gentoo systems. But hey, expect hyphen on 3.8. -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Underscores in USE flags
On 9/20/19 8:46 AM, Mike Gilbert wrote: > Recently, a large number of bugs were filed against packages that have > USE flag names which contain underscores. Apparently PMS prohibits > this except when the USE flag is part of a USE_EXPAND variable. > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > I'm not certain when this text was added to PMS, or how many of the > affected USE flags pre-date this policy. > > Portage seems to have no issue dealing with underscores, so this > doesn't seem to be solving any technical problem. > > I am pretty sure that renaming a bunch of USE flags will cause some > amount of end-user confusion, for very little benefit. Is enforcing > this part of PMS really worth it? If we take this underscore rule to its logical extreme, then we should rename python_targets_python3_7 to python_targets_python3-7, yes? -- Thanks, Zac signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Underscores in USE flags
On Fri, 2019-09-20 at 16:18 -0400, Mike Gilbert wrote: > On Fri, Sep 20, 2019 at 4:03 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 13:24 -0400, Mike Gilbert wrote: > > > On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > > > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny > > > > > wrote: > > > > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > > > > Recently, a large number of bugs were filed against packages that > > > > > > > have > > > > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > > > > > > > I'm not certain when this text was added to PMS, or how many of > > > > > > > the > > > > > > > affected USE flags pre-date this policy. > > > > > > > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > > > > doesn't seem to be solving any technical problem. > > > > > > > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause > > > > > > > some > > > > > > > amount of end-user confusion, for very little benefit. Is > > > > > > > enforcing > > > > > > > this part of PMS really worth it? > > > > > > > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > > > > USE_EXPAND is less confusing to the users? > > > > > > > > > > I doubt users immediately think "USE_EXPAND" when they see an > > > > > underscore. > > > > > > > > > > Portage's seems fairly unambiguous to me. For example: > > > > > > > > > > % emerge -pv1O app-misc/foo > > > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > > > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > > > > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > > > > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > > > > value given the above. > > > > > > > > > > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > > > > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > > > > Expect that they won't work as USE_EXPAND, user typing: > > > > > > > > AWS_TARGETS="foo bar baz" > > > > > > > > will just wildly confused, and in the end this prefixing is just silly > > > > and causes the flag names to become awfully long. > > > > > > Ok, so you chery-picked one particularly horrible example. The Portage > > > output still puts them in USE="" section, though the user probably > > > won't see that given the massive USE flag list. > > > > > > My point still stands for many of the other packages in the repo that > > > don't have several dozen flags. > > > > > > > I'm sorry to say but you can't expect automated software to be able to > > distinguish a 'not horrible' vs 'horrible' use. The test catches both > > cases. The latter case deserves fixing, the former usually involves 1-2 > > flag, so there's no harm in changing it. If for no other reason, then > > to improve consistency in USE flags and save shift key a bit. > > > > The hyphen variant is already in the majority in global flags. What's > > the harm in having local flags match that? > > I'm just trying to minimize pain for people who have flags set in > make.conf and package.use. > I don't see why we couldn't introduce usemove for this purpose. Of course, that's going to work properly only if people don't use wildcards in package.use, and if we rename the flag in all versions simultaneously. -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Underscores in USE flags
On Fri, Sep 20, 2019 at 4:03 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 13:24 -0400, Mike Gilbert wrote: > > On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > > > Recently, a large number of bugs were filed against packages that > > > > > > have > > > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > > > > affected USE flags pre-date this policy. > > > > > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > > > doesn't seem to be solving any technical problem. > > > > > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > > > > amount of end-user confusion, for very little benefit. Is enforcing > > > > > > this part of PMS really worth it? > > > > > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > > > USE_EXPAND is less confusing to the users? > > > > > > > > I doubt users immediately think "USE_EXPAND" when they see an > > > > underscore. > > > > > > > > Portage's seems fairly unambiguous to me. For example: > > > > > > > > % emerge -pv1O app-misc/foo > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > > > value given the above. > > > > > > > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > > > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > > > Expect that they won't work as USE_EXPAND, user typing: > > > > > > AWS_TARGETS="foo bar baz" > > > > > > will just wildly confused, and in the end this prefixing is just silly > > > and causes the flag names to become awfully long. > > > > Ok, so you chery-picked one particularly horrible example. The Portage > > output still puts them in USE="" section, though the user probably > > won't see that given the massive USE flag list. > > > > My point still stands for many of the other packages in the repo that > > don't have several dozen flags. > > > > I'm sorry to say but you can't expect automated software to be able to > distinguish a 'not horrible' vs 'horrible' use. The test catches both > cases. The latter case deserves fixing, the former usually involves 1-2 > flag, so there's no harm in changing it. If for no other reason, then > to improve consistency in USE flags and save shift key a bit. > > The hyphen variant is already in the majority in global flags. What's > the harm in having local flags match that? I'm just trying to minimize pain for people who have flags set in make.conf and package.use.
Re: [gentoo-dev] Underscores in USE flags
On Fri, Sep 20, 2019 at 3:03 PM Haelwenn (lanodan) Monnier wrote: > > [2019-09-20 13:24:45-0400] Mike Gilbert: > > On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > > > Recently, a large number of bugs were filed against packages that > > > > > > have > > > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > > > > affected USE flags pre-date this policy. > > > > > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > > > doesn't seem to be solving any technical problem. > > > > > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > > > > amount of end-user confusion, for very little benefit. Is enforcing > > > > > > this part of PMS really worth it? > > > > > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > > > USE_EXPAND is less confusing to the users? > > > > > > > > I doubt users immediately think "USE_EXPAND" when they see an > > > > underscore. > > > > > > > > Portage's seems fairly unambiguous to me. For example: > > > > > > > > % emerge -pv1O app-misc/foo > > > > > > > > These are the packages that would be merged, in order: > > > > > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > > > value given the above. > > > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > > > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > > > Expect that they won't work as USE_EXPAND, user typing: > > > > > > AWS_TARGETS="foo bar baz" > > > > > > will just wildly confused, and in the end this prefixing is just silly > > > and causes the flag names to become awfully long. > > > > Ok, so you chery-picked one particularly horrible example. The Portage > > output still puts them in USE="" section, though the user probably > > won't see that given the massive USE flag list. > > > > My point still stands for many of the other packages in the repo that > > don't have several dozen flags. > > While that's true for portage, it is false for gentoolkit with the > `equery u ` command. > > Following your original example it would be something like: > > % equery y app-misc/foo > [ Legend : U - final flag setting for installation] > [: I - package is installed with flag ] > [ Colors : set, unset ] > * Found these USE flags for app-misc/foo-0::local > U I > - - modern_kernel: Install init scripts for 3.18 or higher > kernels with atomic rule updates > + + python_targets_python3_7 : Build with Python 3.7 > - - video_cards_radeon : VIDEO_CARDS setting to build driver for ATI > radeon video cards > > And with a bunch more of USE flags (not with having to go to extremes like > dev-libs/aws-sdk-cpp) it is very confusing a lot of time on machines where > app-portage/eix would be overkill I had to check on another machine. Ah, thank you for the example. I imagine equery is used quite frequently for this sort of thing, so I'll concede the point. It would be nice if there were some easy way to migrate package.use settings; that's going to cause some grumbling from sysadmins.
Re: [gentoo-dev] Underscores in USE flags
On Fri, 2019-09-20 at 13:24 -0400, Mike Gilbert wrote: > On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > > Recently, a large number of bugs were filed against packages that have > > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > > > affected USE flags pre-date this policy. > > > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > > doesn't seem to be solving any technical problem. > > > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > > > amount of end-user confusion, for very little benefit. Is enforcing > > > > > this part of PMS really worth it? > > > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > > USE_EXPAND is less confusing to the users? > > > > > > I doubt users immediately think "USE_EXPAND" when they see an underscore. > > > > > > Portage's seems fairly unambiguous to me. For example: > > > > > > % emerge -pv1O app-misc/foo > > > > > > These are the packages that would be merged, in order: > > > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > > value given the above. > > > > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > > Expect that they won't work as USE_EXPAND, user typing: > > > > AWS_TARGETS="foo bar baz" > > > > will just wildly confused, and in the end this prefixing is just silly > > and causes the flag names to become awfully long. > > Ok, so you chery-picked one particularly horrible example. The Portage > output still puts them in USE="" section, though the user probably > won't see that given the massive USE flag list. > > My point still stands for many of the other packages in the repo that > don't have several dozen flags. > I'm sorry to say but you can't expect automated software to be able to distinguish a 'not horrible' vs 'horrible' use. The test catches both cases. The latter case deserves fixing, the former usually involves 1-2 flag, so there's no harm in changing it. If for no other reason, then to improve consistency in USE flags and save shift key a bit. The hyphen variant is already in the majority in global flags. What's the harm in having local flags match that? -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] Underscores in USE flags
[2019-09-20 13:24:45-0400] Mike Gilbert: > On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > > Recently, a large number of bugs were filed against packages that have > > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > > > affected USE flags pre-date this policy. > > > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > > doesn't seem to be solving any technical problem. > > > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > > > amount of end-user confusion, for very little benefit. Is enforcing > > > > > this part of PMS really worth it? > > > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > > USE_EXPAND is less confusing to the users? > > > > > > I doubt users immediately think "USE_EXPAND" when they see an underscore. > > > > > > Portage's seems fairly unambiguous to me. For example: > > > > > > % emerge -pv1O app-misc/foo > > > > > > These are the packages that would be merged, in order: > > > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > > value given the above. > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > > Expect that they won't work as USE_EXPAND, user typing: > > > > AWS_TARGETS="foo bar baz" > > > > will just wildly confused, and in the end this prefixing is just silly > > and causes the flag names to become awfully long. > > Ok, so you chery-picked one particularly horrible example. The Portage > output still puts them in USE="" section, though the user probably > won't see that given the massive USE flag list. > > My point still stands for many of the other packages in the repo that > don't have several dozen flags. While that's true for portage, it is false for gentoolkit with the `equery u ` command. Following your original example it would be something like: % equery y app-misc/foo [ Legend : U - final flag setting for installation] [: I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-misc/foo-0::local U I - - modern_kernel: Install init scripts for 3.18 or higher kernels with atomic rule updates + + python_targets_python3_7 : Build with Python 3.7 - - video_cards_radeon : VIDEO_CARDS setting to build driver for ATI radeon video cards And with a bunch more of USE flags (not with having to go to extremes like dev-libs/aws-sdk-cpp) it is very confusing a lot of time on machines where app-portage/eix would be overkill I had to check on another machine.
Re: [gentoo-dev] Underscores in USE flags
On Fri, Sep 20, 2019 at 12:55 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > > Recently, a large number of bugs were filed against packages that have > > > > USE flag names which contain underscores. Apparently PMS prohibits > > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > > affected USE flags pre-date this policy. > > > > > > > > Portage seems to have no issue dealing with underscores, so this > > > > doesn't seem to be solving any technical problem. > > > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > > amount of end-user confusion, for very little benefit. Is enforcing > > > > this part of PMS really worth it? > > > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > > USE_EXPAND is less confusing to the users? > > > > I doubt users immediately think "USE_EXPAND" when they see an underscore. > > > > Portage's seems fairly unambiguous to me. For example: > > > > % emerge -pv1O app-misc/foo > > > > These are the packages that would be merged, in order: > > > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > > > Total: 1 package (1 new), Size of downloads: 0 KiB > > > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > > value given the above. > > > > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all > start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. > Expect that they won't work as USE_EXPAND, user typing: > > AWS_TARGETS="foo bar baz" > > will just wildly confused, and in the end this prefixing is just silly > and causes the flag names to become awfully long. Ok, so you chery-picked one particularly horrible example. The Portage output still puts them in USE="" section, though the user probably won't see that given the massive USE flag list. My point still stands for many of the other packages in the repo that don't have several dozen flags.
Re: [gentoo-dev] Underscores in USE flags
On Fri, 2019-09-20 at 12:41 -0400, Mike Gilbert wrote: > On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > > Recently, a large number of bugs were filed against packages that have > > > USE flag names which contain underscores. Apparently PMS prohibits > > > this except when the USE flag is part of a USE_EXPAND variable. > > > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > > > I'm not certain when this text was added to PMS, or how many of the > > > affected USE flags pre-date this policy. > > > > > > Portage seems to have no issue dealing with underscores, so this > > > doesn't seem to be solving any technical problem. > > > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > > amount of end-user confusion, for very little benefit. Is enforcing > > > this part of PMS really worth it? > > > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > > USE_EXPAND is less confusing to the users? > > I doubt users immediately think "USE_EXPAND" when they see an underscore. > > Portage's seems fairly unambiguous to me. For example: > > % emerge -pv1O app-misc/foo > > These are the packages that would be merged, in order: > > [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" > PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB > > Total: 1 package (1 new), Size of downloads: 0 KiB > > I don't think anyone would mistake "modern_kernel" for a USE_EXPAND > value given the above. > Look at the humongous list of flags on dev-libs/aws-sdk-cpp. They all start with 'aws_targets' which is a clear attempt to emulate USE_EXPAND. Expect that they won't work as USE_EXPAND, user typing: AWS_TARGETS="foo bar baz" will just wildly confused, and in the end this prefixing is just silly and causes the flag names to become awfully long. -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part
Re: [gentoo-dev] UID/GID assignment for kibana
On Fri, Sep 20, 2019 at 6:36 PM Joonas Niilola wrote: > Hey, > > > On 9/20/19 7:12 PM, Tomas Mozes wrote: > > Hi there, > > while trying to implement glep 81 for kibana I found out that Arch > > Linux uses uid 183 for it, but it's taken by qmail.eclass. Should a > > new uid/gid be taken or it's safe to assume no one will mix kibana > > with qmail? > > > > > I can't find this info anywhere. There's a pull request currently open > for acct-*/qmail stuff, that seems to reserve 200+ for it (like shown in > uid-gid.txt). Nothing seems to reserve 183 as far as I can tell? > > - https://gitweb.gentoo.org/data/api.git/tree/files/uid-gid.txt > > - > > https://github.com/gentoo/gentoo/pull/12898/files#diff-bb8c77449e92c212844f37fc9a56e12aL105 > > > -- juippis > > > Oh I'm sorry, I'm also working on elasticsearch which will have uid/gid 183. Kibana in Arch uses uid 206 and that conflicts with qmails. Tomas
Re: [gentoo-dev] Underscores in USE flags
On Fri, Sep 20, 2019 at 12:11 PM Michał Górny wrote: > > On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > > Recently, a large number of bugs were filed against packages that have > > USE flag names which contain underscores. Apparently PMS prohibits > > this except when the USE flag is part of a USE_EXPAND variable. > > > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > > > I'm not certain when this text was added to PMS, or how many of the > > affected USE flags pre-date this policy. > > > > Portage seems to have no issue dealing with underscores, so this > > doesn't seem to be solving any technical problem. > > > > I am pretty sure that renaming a bunch of USE flags will cause some > > amount of end-user confusion, for very little benefit. Is enforcing > > this part of PMS really worth it? > > And having packages with pretended-USE_EXPAND-that-does-not-work-as- > USE_EXPAND is less confusing to the users? I doubt users immediately think "USE_EXPAND" when they see an underscore. Portage's seems fairly unambiguous to me. For example: % emerge -pv1O app-misc/foo These are the packages that would be merged, in order: [ebuild N ] app-misc/foo-0::local USE="-modern_kernel" PYTHON_TARGETS="python3_7" VIDEO_CARDS="radeon" 0 KiB Total: 1 package (1 new), Size of downloads: 0 KiB I don't think anyone would mistake "modern_kernel" for a USE_EXPAND value given the above.
Re: [gentoo-dev] UID/GID assignment for kibana
Hey, On 9/20/19 7:12 PM, Tomas Mozes wrote: Hi there, while trying to implement glep 81 for kibana I found out that Arch Linux uses uid 183 for it, but it's taken by qmail.eclass. Should a new uid/gid be taken or it's safe to assume no one will mix kibana with qmail? I can't find this info anywhere. There's a pull request currently open for acct-*/qmail stuff, that seems to reserve 200+ for it (like shown in uid-gid.txt). Nothing seems to reserve 183 as far as I can tell? - https://gitweb.gentoo.org/data/api.git/tree/files/uid-gid.txt - https://github.com/gentoo/gentoo/pull/12898/files#diff-bb8c77449e92c212844f37fc9a56e12aL105 -- juippis
[gentoo-dev] UID/GID assignment for kibana
Hi there, while trying to implement glep 81 for kibana I found out that Arch Linux uses uid 183 for it, but it's taken by qmail.eclass. Should a new uid/gid be taken or it's safe to assume no one will mix kibana with qmail? Thanks, Tomas
Re: [gentoo-dev] Underscores in USE flags
On Fri, 2019-09-20 at 11:46 -0400, Mike Gilbert wrote: > Recently, a large number of bugs were filed against packages that have > USE flag names which contain underscores. Apparently PMS prohibits > this except when the USE flag is part of a USE_EXPAND variable. > > https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 > > I'm not certain when this text was added to PMS, or how many of the > affected USE flags pre-date this policy. > > Portage seems to have no issue dealing with underscores, so this > doesn't seem to be solving any technical problem. > > I am pretty sure that renaming a bunch of USE flags will cause some > amount of end-user confusion, for very little benefit. Is enforcing > this part of PMS really worth it? And having packages with pretended-USE_EXPAND-that-does-not-work-as- USE_EXPAND is less confusing to the users? -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part
[gentoo-dev] Underscores in USE flags
Recently, a large number of bugs were filed against packages that have USE flag names which contain underscores. Apparently PMS prohibits this except when the USE flag is part of a USE_EXPAND variable. https://projects.gentoo.org/pms/7/pms.html#x1-23.1.4 I'm not certain when this text was added to PMS, or how many of the affected USE flags pre-date this policy. Portage seems to have no issue dealing with underscores, so this doesn't seem to be solving any technical problem. I am pretty sure that renaming a bunch of USE flags will cause some amount of end-user confusion, for very little benefit. Is enforcing this part of PMS really worth it?
Re: [gentoo-dev] Packages up for grabs due to cardoe being MIA
On 9/13/19 10:25 AM, The Bit Pit wrote: On 9/13/19 9:44 AM, Michał Górny wrote: Hello, The following packages are now up for grabs since Undertakers have not received any reply nor seen any activity from cardoe: media-libs/libhdhomerun [v] I use media-libs/libhdhomerun with mythtv. I can update and test this device so i'll grab it. I submitted a PR to version bump media-tv/mythtv recently. it is still pending... Version bump upstream ebuild now in gentoo repo media-tv/ivtv-utils Mythtv can use this too, but I do not have one to test on. Support for these devices is in v4l2. Source not available from Fedora anymore. sys-firmware/ivtv-firmware Probably in v4l2. Download page is empty. x11-misc/vdpauinfo [v] I use this with mythtv and can test it. This is current and still works with some NVIDIA cards. (I have one) x11-themes/echo-icon-theme Source not available from Fedora anymore.
