Bug 605544 – app-admin/localepurge-0.5.4-r2 : installs into paths that should be created at runtime

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Toralf Förster 2017-01-13 08:48:35 UTC]

QA: other
QA Notice: This ebuild installs into paths that should be created at runtime.
 To fix, simply do not install into these directories.  Instead, your package
 should create dirs on the fly at runtime as needed via init scripts/etc...

  var/cache
  var/cache/localepurge
  var/cache/localepurge/localelist
  var/cache/localepurge/defaultlist

  -----------------------------------------------------------------

  This is an stable amd64 chroot image (named desktop-libressl-stable_20170107-114550) at a hardened host acting as a tinderbox.

  -----------------------------------------------------------------

[Comment 1 Amy Liffey 2017-02-22 13:03:43 UTC]

Hello, 
Are you still willing to maintain this package?

[Comment 2 Jonas Stein 2017-07-25 14:17:12 UTC]

 * unmaintained
 * open bugs
 * no upstream activity https://cgit.gentoo.org/proj/localepurge.git

[Comment 3 Pacho Ramos 2017-07-25 14:37:51 UTC]

Probably we will need to send a mail to gentoo-dev at first before I guess that people will still want to use it. I don't remember what was finally the best alternative :/, I know mgorny was working on improving the locales issue... was relying on INSTALL_MASK the preferred option?

[Comment 4 Michał Górny 2017-07-25 14:53:16 UTC]

Kinda. INSTALL_MASK certainly provides better opportunities than custom tools.

However, my patches to Portage got stuck for some complex technical reason but I don't really remember what it was. I'm using them locally for years now but I don't know if anybody will care enough to get them to Portage now.

[Comment 5 Pacho Ramos 2018-01-04 10:48:11 UTC]

@Michal, any updated on the INSTALL_MASK replacement? Thanks :)

[Comment 6 Michał Górny 2018-01-04 11:36:45 UTC]

Nope. I'll try to ask Zac today why was it stalled.

[Comment 7 Pacho Ramos 2018-03-28 19:02:38 UTC]

*** Bug 651338 has been marked as a duplicate of this bug. ***

[Comment 8 Pacho Ramos 2018-11-04 13:41:24 UTC]

(In reply to Michał Górny from comment #6)
> Nope. I'll try to ask Zac today why was it stalled.

Any news on this? Thanks :)

[Comment 9 Michał Górny 2018-11-04 15:22:34 UTC]

(In reply to Pacho Ramos from comment #8)
> (In reply to Michał Górny from comment #6)
> > Nope. I'll try to ask Zac today why was it stalled.
> 
> Any news on this? Thanks :)

The most important part is merged already.  I think I didn't push for well-defined path list but I suppose that's not a killer feature here.

[Comment 10 Pacho Ramos 2018-11-04 15:31:49 UTC]

OK, thanks

What would be the best tip for localepurge users then when masking it? Manually setting INSTALL_MASK? Relying on app-portage/install-mask?

[Comment 11 Michał Górny 2018-11-04 16:00:38 UTC]

Manually, I think.  Something along the lines of:

  INSTALL_MASK="/usr/share/locale -/usr/share/locale/foo"

I'd appreciate if you could confirm that it works correctly with stable Portage.

[Comment 12 Pacho Ramos 2018-11-04 17:43:46 UTC]

At least with latest stable sys-apps/portage-2.3.51 is seems to work nice ;)

[Comment 13 Luca Santarelli 2018-11-24 10:46:47 UTC]

With all due respect, forgive me for my ignorance but what is the proper syntax for INSTALL_MASK to support two locales? Could an example be put in the package.mask file? I tried

INSTALL_MASK="/usr/share/locale -/usr/share/locale/it -/usr/share/locale/en"

but I ended up with only the it locale installed.

make.conf.example reports:

# INSTALL_MASK allows certain files to not be installed into your file system.
#     This is useful when you wish to filter out a certain set of files from
#     ever being installed, such as INSTALL.gz or TODO.gz
#INSTALL_MASK=""

[Comment 14 Michał Górny 2018-12-11 13:57:15 UTC]

Removing wrt #183273.