Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Haelwenn (lanodan) Monnier
[2019-08-11 14:53:34+0200] Michał Górny:
> On Sun, 2019-08-11 at 14:46 +0300, Mart Raudsepp wrote:
> > The USE flag naming feels a bit to be desired by me.
> > That's because I don't believe in USE flags having to be named by the
> > external dep they introduce, but by functionality. USE=magic sounds
> > like a USE flag that adds some wizards into your application, automagic
> > behavior or who knows (until you read the description).
> > Not that I have a much better suggestion. USE=auto-mimetypes?
> > 
> 
> The use of term 'magic' for file type recognition by magic bytes is well
> established.

Yes, but `magic` doesn't really gives much of an idea on the feature 
and could get a bit of confusion, I think `libmagic` is better on this 
regard as it's closer to what would be used without much context and 
it's clear that it's about a dependency on sys-apps/file and not some 
kind of magic feature (which is a quite overloaded word in computing).

(auto-mimetype doesn't works at all btw, file/libmagic is much more 
precise than mimetypes)



Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread Michał Górny
On Sun, 2019-08-11 at 17:53 -0500, William Hubbs wrote:
> On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs  wrote:
> > > If we are going to require a modeline, shouldn't we consider allowing
> > > them by default so we can work out of the box instead of having to tweak
> > > our editor settings?
> > 
> > Perhaps we should. Is this really an important point for you?
> > 
> > I don't think any of that needs to hold up Michał's proposal though.
> 
> Let's move away from talking about alignment for a minute.
> 
> The reason I responded originally was that his proposal is a bit
> vague. It says that whitespace separates fields; that could be spaces
> or tabs. whitespace can also be a completely valid character in
> the notes field. So, since he says we can add more fields in the future,
> you either have to escape whitespace in the notes field or quote the
> field.

We can add new fields *in the middle*.  That's why there's explicit
header line.

> Also, he may have used one whitespace character to separate fields in his
> example, but the spec allows any number of whitespace characters.
> 

awk does not have a problem with that.


-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread Matt Turner
On Sun, Aug 11, 2019 at 3:54 PM William Hubbs  wrote:
>
> On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> > On Sun, Aug 11, 2019 at 12:48 PM William Hubbs  wrote:
> > > If we are going to require a modeline, shouldn't we consider allowing
> > > them by default so we can work out of the box instead of having to tweak
> > > our editor settings?
> >
> > Perhaps we should. Is this really an important point for you?
> >
> > I don't think any of that needs to hold up Michał's proposal though.
>
> Let's move away from talking about alignment for a minute.
>
> The reason I responded originally was that his proposal is a bit
> vague. It says that whitespace separates fields; that could be spaces
> or tabs. whitespace can also be a completely valid character in
> the notes field. So, since he says we can add more fields in the future,
> you either have to escape whitespace in the notes field or quote the
> field.
>
> Also, he may have used one whitespace character to separate fields in his
> example, but the spec allows any number of whitespace characters.

Sigh.

The intention is to make it easily machine parseable and easily
readable by humans.

One or more whitespace characters is easy to recognize by a machine,
be they space or tabs. Aligned columns are easily readable by humans.
I think humans are able to follow existing convention when adding new
lines to the file and don't require specific rules like this.

There's nothing unclear or vague in his explanation. Can we please proceed?



[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2019-08-11 23:59 UTC

2019-08-11 Thread Robin H. Johnson
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2019-08-11 23:59 UTC.

Removals:
dev-scheme/guile-gui20190810-04:02 mattst88   4d959b2fc99
dev-scheme/guile-www20190810-04:02 mattst88   21a04a6c7a6
dev-scheme/net-http 20190810-04:02 mattst88   792f034dede
sci-chemistry/coot  20190810-04:03 mattst88   c399a8bb15a
sci-chemistry/reduce20190810-04:03 mattst88   a3ffd565b7b
sci-libs/cctbx  20190810-04:03 mattst88   a57dee12f49
sci-libs/clipper20190810-04:03 mattst88   a3fbf8343b9
sci-libs/coot-data  20190810-04:03 mattst88   c5919e73bf4
sci-libs/gpp4   20190810-04:04 mattst88   9bae8cdca3c
sci-libs/libccp420190810-04:04 mattst88   e36dc81141b
sci-libs/mmdb   20190810-04:04 mattst88   d622a8cb8c0
sci-libs/monomer-db 20190810-04:04 mattst88   aa1dd6fdcda
sci-libs/ssm20190810-04:04 mattst88   2f089f12008
sys-apps/light  20190809-08:34 chainsaw   7f324bfd6ea

Additions:
acct-group/logstash 20190727-17:31 juippis4e3dd455178
acct-group/minecraft20190806-18:30 juippis27e0bc11dd1
acct-group/polkitd  20190809-17:08 floppym54dfa6e2c0d
acct-group/transmission 20190805-01:06 floppym567b7e06497
acct-group/unrealircd   20190804-09:19 kensington 40bf2da200d
acct-user/logstash  20190727-17:32 juippise6b6ef9025c
acct-user/minecraft 20190806-18:31 juippisc2547f538a0
acct-user/polkitd   20190809-17:09 floppym381c9615acc
acct-user/transmission  20190805-01:07 floppym7bb4cf39be0
acct-user/unrealircd20190804-09:23 kensington 8b17f69e954
app-crypt/virtualsmartcard  20190809-22:12 mgorny 97daa7ed391
app-misc/cfiles 20190726-07:03 alicef 94642b1c49e
app-misc/pip3line   20190805-09:37 zlogenef4f65d45f22
dev-libs/rocm-comgr 20190731-15:53 candrews   c0aa27dab03
dev-libs/rocm-device-libs   20190726-20:34 candrews   333d0df0bb1
dev-libs/rocm-hostcall  20190731-15:22 candrews   b8ca3b0862e
dev-libs/rocm-opencl-driver 20190726-18:21 candrews   98d3c369ac7
dev-util/rocm-cmake 20190725-19:45 candrews   8f1b624402f
dev-util/rocminfo   20190725-22:02 candrews   95977d266eb
gui-apps/grim   20190804-03:33 bman   264467e31b7
gui-apps/slurp  20190804-03:39 bman   18a65ca991f
sci-libs/dealii 20190805-06:28 tamiko ecf7fa5aeab
sci-libs/gmsh   20190805-05:42 tamiko d391eb27ea4
sci-libs/med20190805-05:40 tamiko e6160959088
sci-libs/trilinos   20190805-06:15 tamiko 0c6704f8b7f
sci-mathematics/petsc   20190805-04:48 tamiko 44c266fd90f
sci-mathematics/slepc   20190805-04:53 tamiko ea0a668c188
sys-apps/light  20190808-13:33 chainsaw   5065c619831
sys-cluster/kube-router 20190721-15:01 maksbotan  c01c2d2e17f
sys-devel/llvm-roc  20190726-18:15 candrews   5b5b9c1a381
sys-process/uksmd   20190808-14:35 juippisb6025b7c968

--
Robin Hugh Johnson
Gentoo Linux Developer
E-Mail : robb...@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85
Removed Packages:
sci-libs/ssm,removed,mattst88,20190810-04:04,2f089f12008
sci-libs/monomer-db,removed,mattst88,20190810-04:04,aa1dd6fdcda
sci-libs/mmdb,removed,mattst88,20190810-04:04,d622a8cb8c0
sci-libs/libccp4,removed,mattst88,20190810-04:04,e36dc81141b
sci-libs/gpp4,removed,mattst88,20190810-04:04,9bae8cdca3c
sci-libs/coot-data,removed,mattst88,20190810-04:03,c5919e73bf4
sci-libs/clipper,removed,mattst88,20190810-04:03,a3fbf8343b9
sci-libs/cctbx,removed,mattst88,20190810-04:03,a57dee12f49
sci-chemistry/reduce,removed,mattst88,20190810-04:03,a3ffd565b7b
sci-chemistry/coot,removed,mattst88,20190810-04:03,c399a8bb15a
dev-scheme/net-http,removed,mattst88,20190810-04:02,792f034dede
dev-scheme/guile-www,removed,mattst88,20190810-04:02,21a04a6c7a6
dev-scheme/guile-gui,removed,mattst88,20190810-04:02,4d959b2fc99
sys-apps/light,removed,chainsaw,20190809-08:34,7f324bfd6ea
Added Packages:
acct-user/logstash,added,juippis,20190727-17:32,e6b6ef9025c
acct-group/logstash,added,juippis,20190727-17:31,4e3dd455178
app-crypt/virtualsmartcard,added,mgorny,20190809-22:12,97daa7ed391
app-misc/cfiles,added,alicef,20190726-07:03,94642b1c49e
acct-user/polkitd,added,floppym,20190809-17:09,381c9615acc
acct-group/polkitd,added,floppym,20190809-17:08,54dfa6e2c0d
gui-apps/slurp,added,bman,20190804-03:39,18a65ca991f
gui-apps/grim,added,bman,20190804-03:33,264467e31b7
sys-process/uksmd,added,juippis,20190808-14:35,b6025b7c968
sys-apps/light,added,chainsaw,20190808-13:33,5065c619831
dev-libs/rocm-comgr,added,candrews,20190731-15:53,c0aa27dab03
dev-libs/rocm-hostcall,added,candrews,20190731-15:22,b8ca3b0862e
dev-libs/rocm-device-libs,added,candrews,20190726-20:34,333d0df0bb1

Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread William Hubbs
On Sun, Aug 11, 2019 at 03:04:02PM -0700, Matt Turner wrote:
> On Sun, Aug 11, 2019 at 12:48 PM William Hubbs  wrote:
> > If we are going to require a modeline, shouldn't we consider allowing
> > them by default so we can work out of the box instead of having to tweak
> > our editor settings?
> 
> Perhaps we should. Is this really an important point for you?
> 
> I don't think any of that needs to hold up Michał's proposal though.

Let's move away from talking about alignment for a minute.

The reason I responded originally was that his proposal is a bit
vague. It says that whitespace separates fields; that could be spaces
or tabs. whitespace can also be a completely valid character in
the notes field. So, since he says we can add more fields in the future,
you either have to escape whitespace in the notes field or quote the
field.

Also, he may have used one whitespace character to separate fields in his
example, but the spec allows any number of whitespace characters.

William


signature.asc
Description: Digital signature


Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread Matt Turner
On Sun, Aug 11, 2019 at 12:48 PM William Hubbs  wrote:
>
> On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
> > On Sat, Aug 10, 2019 at 1:49 PM William Hubbs  wrote:
> > >
> > > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > > > Hi,
> > > >
> > > > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > > > to something more accessible.  I've finally gotten around to draft
> > > > something, and I'd like to hear your comments about it.  The idea is to
> > > > keep a whitespace-separated record format file in api.gentoo.org repo.
> > > >
> > > > This is mostly inspired by Fedora's format, specifically the ability to
> > > > specify both UID and GID for matching user/group on the same line.
> > > > I've also decided not to attempt to specify disjoint Linux and FreeBSD
> > > > users/groups on a single line.  Instead, they are specified separately
> > > > and defined by providers (as suggested by Ulrich).
> > > >
> > > > Sample, along with big comment explaining the file format, below.
> > >
> > > I'm not sure how I feel about whitespace delimiters for this. withno
> > > further specification, it would make these two lines completely valid:
> > >
> > > root 0 0 baselayout
> > > bin 1   1   
> > > baselayout  some notes here
> >
> > That's true, but I think with editor settings embedded in the file and
> > visual pattern of vertical alignment we shouldn't expect a bunch of
> > problems.
>
> We don't honor editor settings in files by default, so this will not
> work out of the box (see this in /etc/vim/vimrc).
>
> --- cut here ---
> " {{{ Modeline settings
> " We don't allow modelines by default. See bug #14088 and bug #73715.
> " If you're not concerned about these, you can enable them on a per-user
> " basis by adding "set modeline" to your ~/.vimrc file.
> set nomodeline
> " }}}
> --- cut here ---
>
> If we are going to require a modeline, shouldn't we consider allowing
> them by default so we can work out of the box instead of having to tweak
> our editor settings?

Perhaps we should. Is this really an important point for you?

I don't think any of that needs to hold up Michał's proposal though.



[gentoo-dev] [PATCH] profiles/desc: Add L10N locales from www-client/vivaldi*

2019-08-11 Thread David Seifert
USE_EXPAND flags have to be defined globally by PMS. Sending this in because
jer is unwilling to work with the QA team in improving QA violations.




[gentoo-dev] [PATCH] profiles/desc: Add L10N locales from www-client/vivaldi*

2019-08-11 Thread David Seifert
Bug: https://bugs.gentoo.org/689482
Signed-off-by: David Seifert 
---
 profiles/desc/l10n.desc | 4 
 1 file changed, 4 insertions(+)

diff --git a/profiles/desc/l10n.desc b/profiles/desc/l10n.desc
index 3797fc41527..a21502a83c4 100644
--- a/profiles/desc/l10n.desc
+++ b/profiles/desc/l10n.desc
@@ -73,6 +73,7 @@ es-AR - Spanish (Argentina)
 es-CL - Spanish (Chile)
 es-ES - Spanish (Spain)
 es-MX - Spanish (Mexico)
+es-PE - Spanish (Peru)
 et - Estonian
 eu - Basque
 fa - Persian
@@ -98,10 +99,12 @@ hu - Hungarian
 hy - Armenian
 ia - Interlingua
 id - Indonesian
+io - Ido
 is - Icelandic
 it - Italian
 iu - Inuktitut
 ja - Japanese
+jbo - Lojban
 jv - Javanese
 ka - Georgian
 kab - Kabyle
@@ -154,6 +157,7 @@ ru - Russian
 rw - Kinyarwanda
 sa - Sanskrit
 sat - Santali
+sc - Sardinian
 sco - Scots
 sd - Sindhi
 si - Sinhala
-- 
2.22.0




Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread William Hubbs
On Sat, Aug 10, 2019 at 05:41:56PM -0700, Matt Turner wrote:
> On Sat, Aug 10, 2019 at 1:49 PM William Hubbs  wrote:
> >
> > On Tue, Aug 06, 2019 at 11:29:50PM +0200, Michał Górny wrote:
> > > Hi,
> > >
> > > Some time ago William asked me to move UID/GID assignments from wiki [1]
> > > to something more accessible.  I've finally gotten around to draft
> > > something, and I'd like to hear your comments about it.  The idea is to
> > > keep a whitespace-separated record format file in api.gentoo.org repo.
> > >
> > > This is mostly inspired by Fedora's format, specifically the ability to
> > > specify both UID and GID for matching user/group on the same line.
> > > I've also decided not to attempt to specify disjoint Linux and FreeBSD
> > > users/groups on a single line.  Instead, they are specified separately
> > > and defined by providers (as suggested by Ulrich).
> > >
> > > Sample, along with big comment explaining the file format, below.
> >
> > I'm not sure how I feel about whitespace delimiters for this. withno
> > further specification, it would make these two lines completely valid:
> >
> > root 0 0 baselayout
> > bin 1   1   baselayout  
> > some notes here
> 
> That's true, but I think with editor settings embedded in the file and
> visual pattern of vertical alignment we shouldn't expect a bunch of
> problems.

We don't honor editor settings in files by default, so this will not
work out of the box (see this in /etc/vim/vimrc).

--- cut here ---
" {{{ Modeline settings
" We don't allow modelines by default. See bug #14088 and bug #73715.
" If you're not concerned about these, you can enable them on a per-user
" basis by adding "set modeline" to your ~/.vimrc file.
set nomodeline
" }}}
--- cut here ---

If we are going to require a modeline, shouldn't we consider allowing
them by default so we can work out of the box instead of having to tweak
our editor settings?

William



signature.asc
Description: Digital signature


[gentoo-dev] [gentoo-dev-announce] Package up for grabs: net-im/mattermost-desktop-bin

2019-08-11 Thread Patrice Clement
Hi

net-im/mattermost-desktop-bin is now up for grabs.

Thanks.

-- 
Patrice Clement
Gentoo Linux developer
http://www.gentoo.org




Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Michał Górny
On Sun, 2019-08-11 at 16:45 +0300, Mart Raudsepp wrote:
> Ühel kenal päeval, P, 11.08.2019 kell 14:53, kirjutas Michał Górny:
> > On Sun, 2019-08-11 at 14:46 +0300, Mart Raudsepp wrote:
> > > The USE flag naming feels a bit to be desired by me.
> > > That's because I don't believe in USE flags having to be named by
> > > the
> > > external dep they introduce, but by functionality. USE=magic sounds
> > > like a USE flag that adds some wizards into your application,
> > > automagic
> > > behavior or who knows (until you read the description).
> > > Not that I have a much better suggestion. USE=auto-mimetypes?
> > > 
> > 
> > The use of term 'magic' for file type recognition by magic bytes is
> > well established.
> 
> Fair enough.
> 
> > Standing on your head and trying to invent an
> > alternative
> > is not going to help anyone, and only confuse people.
> 
> Completely uncalled for unfriendly hostile additional sentence.

I didn't mean to be hostile.  I just meant to visually explain that your
suggestion is long way from the initial point (hence 'standing on your
head'), and it's going to be confusing.

-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part


[gentoo-portage-dev] [PATCH] Allow ESYSROOT and BROOT in the pkg_setup phase

2019-08-11 Thread James Le Cuirot
From: Michał Górny 

This follows a recent change to PMS.

Signed-off-by: James Le Cuirot 
---
 lib/portage/package/ebuild/config.py | 7 ---
 1 file changed, 4 insertions(+), 3 deletions(-)

Sending this on behalf of mgorny as requested.

diff --git a/lib/portage/package/ebuild/config.py 
b/lib/portage/package/ebuild/config.py
index 83a15b370..e0dda54d4 100644
--- a/lib/portage/package/ebuild/config.py
+++ b/lib/portage/package/ebuild/config.py
@@ -2820,12 +2820,13 @@ class config(object):
if not eapi_exports_merge_type(eapi):
mydict.pop("MERGE_TYPE", None)
 
-   src_phase = _phase_func_map.get(phase, '').startswith('src_')
+   src_like_phase = (phase == 'setup' or
+   _phase_func_map.get(phase, 
'').startswith('src_'))
 
-   if not (src_phase and eapi_attrs.sysroot):
+   if not (src_like_phase and eapi_attrs.sysroot):
mydict.pop("ESYSROOT", None)
 
-   if not (src_phase and eapi_attrs.broot):
+   if not (src_like_phase and eapi_attrs.broot):
mydict.pop("BROOT", None)
 
# Prefix variables are supported beginning with EAPI 3, or when
-- 
2.21.0




Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Pacho Ramos
El dom, 11-08-2019 a las 13:21 +0200, Michał Górny escribió:
> USE=magic is currently used consistently by 12 packages:
> 
> app-arch/engrampa[magic] Enable filetype auto-detection via
>   sys-apps/file
> app-editors/nano[magic] Add magic file support (sys-apps/file) to
>   automatically detect appropriate syntax highlighting
> app-misc/vifm[magic] Use libmagic to determine mimetypes
> app-misc/worker[magic] Add magic file support from sys-apps/file to
>   automatically detect file types
> app-text/zathura[magic] Use libmagic to determine mimetypes
> media-gfx/qiv[magic] Use libmagic to determine mimetypes
> media-libs/libextractor[magic] Enable magic support using sys-apps/file
> media-sound/moc[magic] Use libmagic to determine mimetypes
> net-misc/gerbera[magic] Use libmagic to determine file types
> net-p2p/mldonkey[magic] enable use of libmagic
> sci-geosciences/viking[magic] Use libmagic to determine mimetypes
> www-servers/pshs[magic] Enable automatic detection of Content-Type using
>   libmagic (sys-apps/file)

It seems it should also cover, if possible, this to packages that use an
alternative name:

dev-python/jira:filemagic - Include filemagic support (for identifying uploaded
filetypes)
dev-vcs/git-annex:magicmime - Use libmagic to determine file MIME types



signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Mart Raudsepp
Ühel kenal päeval, P, 11.08.2019 kell 14:53, kirjutas Michał Górny:
> On Sun, 2019-08-11 at 14:46 +0300, Mart Raudsepp wrote:
> > The USE flag naming feels a bit to be desired by me.
> > That's because I don't believe in USE flags having to be named by
> > the
> > external dep they introduce, but by functionality. USE=magic sounds
> > like a USE flag that adds some wizards into your application,
> > automagic
> > behavior or who knows (until you read the description).
> > Not that I have a much better suggestion. USE=auto-mimetypes?
> > 
> 
> The use of term 'magic' for file type recognition by magic bytes is
> well established.

Fair enough.

> Standing on your head and trying to invent an
> alternative
> is not going to help anyone, and only confuse people.

Completely uncalled for unfriendly hostile additional sentence.


signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Michał Górny
On Sun, 2019-08-11 at 14:46 +0300, Mart Raudsepp wrote:
> The USE flag naming feels a bit to be desired by me.
> That's because I don't believe in USE flags having to be named by the
> external dep they introduce, but by functionality. USE=magic sounds
> like a USE flag that adds some wizards into your application, automagic
> behavior or who knows (until you read the description).
> Not that I have a much better suggestion. USE=auto-mimetypes?
> 

The use of term 'magic' for file type recognition by magic bytes is well
established.  Standing on your head and trying to invent an alternative
is not going to help anyone, and only confuse people.

-- 
Best regards,
Michał Górny



signature.asc
Description: This is a digitally signed message part


Re: [gentoo-dev] RFC: UID/GID assignment for i2pd (170)

2019-08-11 Thread Alexey I . Korepanov
Changed UID and GID from 170 to 470, because arch linux uses 170 for zabbix. 11.08.2019, 01:51, "Michael Orlitzky" :On 8/10/19 4:27 AM, Alexey I. Korepanov wrote: The process runs as i2pd:i2pd. The group is not used for anything specific.I think I confused myself. The user does need a primary group, in anycase. Everything's fine, carry on. 



Re: [gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Mart Raudsepp
The USE flag naming feels a bit to be desired by me.
That's because I don't believe in USE flags having to be named by the
external dep they introduce, but by functionality. USE=magic sounds
like a USE flag that adds some wizards into your application, automagic
behavior or who knows (until you read the description).
Not that I have a much better suggestion. USE=auto-mimetypes?

Mart


Ühel kenal päeval, P, 11.08.2019 kell 13:21, kirjutas Michał Górny:
> USE=magic is currently used consistently by 12 packages:
> 
> app-arch/engrampa[magic] Enable filetype auto-detection via
>   sys-apps/file
> app-editors/nano[magic] Add magic file support (sys-apps/file) to
>   automatically detect appropriate syntax highlighting
> app-misc/vifm[magic] Use libmagic to determine mimetypes
> app-misc/worker[magic] Add magic file support from sys-apps/file to
>   automatically detect file types
> app-text/zathura[magic] Use libmagic to determine mimetypes
> media-gfx/qiv[magic] Use libmagic to determine mimetypes
> media-libs/libextractor[magic] Enable magic support using sys-
> apps/file
> media-sound/moc[magic] Use libmagic to determine mimetypes
> net-misc/gerbera[magic] Use libmagic to determine file types
> net-p2p/mldonkey[magic] enable use of libmagic
> sci-geosciences/viking[magic] Use libmagic to determine mimetypes
> www-servers/pshs[magic] Enable automatic detection of Content-Type
> using
>   libmagic (sys-apps/file)
> 
> Signed-off-by: Michał Górny 
> ---
>  profiles/use.desc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/profiles/use.desc b/profiles/use.desc
> index 13baef969315..09940dd81822 100644
> --- a/profiles/use.desc
> +++ b/profiles/use.desc
> @@ -181,6 +181,7 @@ lzma - Support for LZMA (de)compression algorithm
>  lzo - Enable support for lzo compression
>  m17n-lib - Enable m17n-lib support
>  mad - Add support for mad (high-quality mp3 decoder library and cli
> frontend)
> +magic - Add support for file type detection via magic bytes (usually
> via libmagic from sys-apps/file)
>  maildir - Add support for maildir (~/.maildir) style mail spools
>  matroska - Add support for the matroska container format (extensions
> .mkv, .mka and .mks)
>  mbox - Add support for mbox (/var/spool/mail) style mail spools


signature.asc
Description: This is a digitally signed message part


[gentoo-dev] [PATCH] use.desc: Introduce global USE=magic

2019-08-11 Thread Michał Górny
USE=magic is currently used consistently by 12 packages:

app-arch/engrampa[magic] Enable filetype auto-detection via
  sys-apps/file
app-editors/nano[magic] Add magic file support (sys-apps/file) to
  automatically detect appropriate syntax highlighting
app-misc/vifm[magic] Use libmagic to determine mimetypes
app-misc/worker[magic] Add magic file support from sys-apps/file to
  automatically detect file types
app-text/zathura[magic] Use libmagic to determine mimetypes
media-gfx/qiv[magic] Use libmagic to determine mimetypes
media-libs/libextractor[magic] Enable magic support using sys-apps/file
media-sound/moc[magic] Use libmagic to determine mimetypes
net-misc/gerbera[magic] Use libmagic to determine file types
net-p2p/mldonkey[magic] enable use of libmagic
sci-geosciences/viking[magic] Use libmagic to determine mimetypes
www-servers/pshs[magic] Enable automatic detection of Content-Type using
  libmagic (sys-apps/file)

Signed-off-by: Michał Górny 
---
 profiles/use.desc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/profiles/use.desc b/profiles/use.desc
index 13baef969315..09940dd81822 100644
--- a/profiles/use.desc
+++ b/profiles/use.desc
@@ -181,6 +181,7 @@ lzma - Support for LZMA (de)compression algorithm
 lzo - Enable support for lzo compression
 m17n-lib - Enable m17n-lib support
 mad - Add support for mad (high-quality mp3 decoder library and cli frontend)
+magic - Add support for file type detection via magic bytes (usually via 
libmagic from sys-apps/file)
 maildir - Add support for maildir (~/.maildir) style mail spools
 matroska - Add support for the matroska container format (extensions .mkv, 
.mka and .mks)
 mbox - Add support for mbox (/var/spool/mail) style mail spools
-- 
2.23.0.rc1




Re: [gentoo-dev] [RFC] Moving UID/GID assignments to api.gentoo.org

2019-08-11 Thread Ulrich Mueller
> On Sun, 11 Aug 2019, William Hubbs wrote:

> Well, I suppose it wouldn't be a problem if we don't care about
> alignment, but that is not readable either really right?

> For example, (completely making up uid/gid numbers), this is totally
> valid.

> root 0 0 baselayout this is from baselayout
> bin 1 1 baselayout this is from baselayout
> postgresql 150 150 app this is from postgresql
> cockroach 250 250 app this is from cockroach

Of course the columns would be aligned, as in Michał's original example.
What is the problem you are you trying to solve?

Ulrich