Re: [gentoo-dev] prepalldocs is now banned

2009-02-17 Thread Alexis Ballier
On Wed, 18 Feb 2009 00:18:06 +
Ciaran McCreesh  wrote:

> On Tue, 17 Feb 2009 19:10:33 -0500
> Michael Sterrett  wrote:
> > So everybody who emerges gnupg since this change is wasting space
> > for no good reason.
> 
> If you care about a couple of hundred kilobytes, relying upon
> individual ebuilds to ask the package manager to compress
> documentation in some arbitrary manner is the wrong solution.

Then, for the nth time, what would be the good solution? How would one
convert prepalldocs usage to something allowed? I've failed to find
anything about it in the relevant bug and the only answer I've seen is
"remove it". You can count on me for marking any prepalldocs removal bug
I'll be the assignee as wontfix as long as there won't be any
alternative solution.

Note that I would consider a viable solution banning prepalldocs and
simply removing it if portage was compressing docs by its own or
calling prepalldocs after src_install... but then IMHO that's the
removal of prepalldocs that would require an EAPI bump not its
reintroduction.


Regards,

Alexis.


signature.asc
Description: PGP signature


Re: [gentoo-dev] prepalldocs is now banned

2009-02-17 Thread Ciaran McCreesh
On Tue, 17 Feb 2009 19:10:33 -0500
Michael Sterrett  wrote:
> So everybody who emerges gnupg since this change is wasting space for
> no good reason.

If you care about a couple of hundred kilobytes, relying upon
individual ebuilds to ask the package manager to compress documentation
in some arbitrary manner is the wrong solution.

This was already discussed at length prior to the Council reaching
their decision.

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [gentoo-dev] prepalldocs is now banned

2009-02-17 Thread Michael Sterrett
Why would people want to blindly remove prepalldocs when it clearly
results in an inferior build of the package?

Take the recent change to the (already marked stable)
gnupg-2.0.9.ebuild as an example:

Before:

$ epm -qi gnupg | grep Size
Size: 2845754

$ epm -qi gnupg | grep Size
Size: 3089515

So everybody who emerges gnupg since this change is wasting space for
no good reason.

Michael Sterrett
 -Mr. Bones.-
mr_bon...@gentoo.org



Re: [gentoo-dev] prepalldocs is now banned

2009-02-17 Thread Thilo Bangert
Thomas Anderson  said:
> Hi Everyone,
>
> This is a note that in the council meeting on 02/12/2009 the
> function 'prepalldocs' is banned for use in ebuilds with EAPIs 0 1
> and 2. If you want some functionality from this function, please
> propose a new function or clearly defined behavior for prepalldocs
> for a *new* EAPI.

we have a tracker bug at:
http://bugs.gentoo.org/show_bug.cgi?id=259422

the following 99 packages currently still use 'prepalldocs'. some time in 
the near future i will start filing individual bugs for each of these. 
feel free to beat me to the punch.

thanks
kind regards
Thilo

app-arch/gtk-splitter   
  
app-arch/rar
  
app-arch/xdms   
  
app-backup/amanda   
  
app-cdr/cdcover 
  
app-crypt/gnupg-pkcs11-scd  
  
app-crypt/steghide  
  
app-doc/howto-text  
  
app-doc/phrack  
  
app-emacs/ess   
  
app-misc/ca-certificates
  
app-misc/emelfm2
  
app-misc/g15daemon  
  
app-misc/g15macro   
  
app-misc/g15message 
  
app-misc/g15mpd 
  
app-misc/g15stats   
  
app-office/gnucash  
  
app-text/htag   
  
app-text/robodoc
  
app-text/sloccount  
  
app-text/ttf2pt1
  
dev-db/myodbc   
  
dev-db/mysql++  
  
dev-db/unixODBC 
  
dev-embedded/sdcc   
  
dev-embedded/uisp   
  
dev-games/flatzebra 
  
dev-lang/gpc
  
dev-libs/libg15render   
  
dev-libs/libgringotts   
  
dev-libs/libmcrypt  
  
dev-libs/pkcs11-helper  
  
dev-libs/ppl
  
dev-python/gst-python   
  
dev-python/yolk 
  
dev-tcltk/mysqltcl  
  
dev-tex/cjk-latex   
  
dev-tex/frakturx
  
dev-util/anjuta 
  
dev-util/geany  
  
dev-util/ltrace 
  
dev-util/pretrace   
  
games-arcade/afternoonstalker  

Re: [gentoo-dev] Time to remove app-shells/bash-completion-config

2009-02-17 Thread Ciaran McCreesh
On Tue, 17 Feb 2009 14:27:24 -0600
Jeremy Olexa  wrote:
> This is not a fault of bash-completion but rather the eselect
> bash-completion module itself. Since our eselect team is defunct, I
> will mask the bash-completion USE flag for app-admin/eselect unless
> someone steps up to take care of it (working patches exist, anyone?).

*cough* fixed in eclectic *cough*

Unfortunately Cardoe hasn't followed through on his plans to move
Gentoo over...

-- 
Ciaran McCreesh


signature.asc
Description: PGP signature


Re: [gentoo-dev] Time to remove app-shells/bash-completion-config

2009-02-17 Thread Jeremy Olexa
On Tue, Feb 17, 2009 at 1:49 PM, Donnie Berkholz  wrote:
> On 11:55 Tue 17 Feb , Jeremy Olexa wrote:
>> We should only be using eselect now to enable bash-completion. I think
>> bash-completion-config is broken now anyway
>> (https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this
>> change, I will p.mask b-c-c for removal.
>>
>> Any concerns? The upgrade path in the future is going to be wierd as
>> upstream is releasing v1.0 soon, but that is not concern for now.
>
> http://bugs.gentoo.org/show_bug.cgi?id=218557
>
> [Comment #0] mescali...@gentoo.org : 2008-04-20 12:26:38 
> ---
> if I type:
>
>  eselect bashcomp enable [TAB]
>
> I get a 'Killed' string printed to terminal:
>
>  eselect bashcomp enable Killed
>
> and it messes up the bash shell (i.e. history doesn't work anymore)
>
> [Comment #3] w.schwie...@web.de : 2008-07-31 00:41:39 
> ---
> Created an attachment (id=161784)
> Replacement for the current eselect completion script

This is not a fault of bash-completion but rather the eselect
bash-completion module itself. Since our eselect team is defunct, I
will mask the bash-completion USE flag for app-admin/eselect unless
someone steps up to take care of it (working patches exist, anyone?).
Analogy: If subversion's bash-completion module was broken, it
wouldn't block anything to do with app-shells/bash-completion. Instead
you would work it out with upstream.

Also: *enabling* bash-completion modules via eselect works just fine.
So, I don't get why this reply was needed on this thread.

-Jeremy



Re: [gentoo-dev] Time to remove app-shells/bash-completion-config

2009-02-17 Thread Donnie Berkholz
On 11:55 Tue 17 Feb , Jeremy Olexa wrote:
> We should only be using eselect now to enable bash-completion. I think
> bash-completion-config is broken now anyway
> (https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this
> change, I will p.mask b-c-c for removal.
> 
> Any concerns? The upgrade path in the future is going to be wierd as
> upstream is releasing v1.0 soon, but that is not concern for now.

http://bugs.gentoo.org/show_bug.cgi?id=218557

[Comment #0] mescali...@gentoo.org : 2008-04-20 12:26:38 
---
if I type:

 eselect bashcomp enable [TAB]

I get a 'Killed' string printed to terminal:

 eselect bashcomp enable Killed

and it messes up the bash shell (i.e. history doesn't work anymore)

[Comment #3] w.schwie...@web.de : 2008-07-31 00:41:39 
---
Created an attachment (id=161784)
Replacement for the current eselect completion script


-- 
Thanks,
Donnie

Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com


pgpKX1tIbc30V.pgp
Description: PGP signature


[gentoo-dev] Time to remove app-shells/bash-completion-config

2009-02-17 Thread Jeremy Olexa
Hello,
I would like to request that bash-completion-20081218 to be marked
stable by the arches soon here.

In doing so, I'm going to make the following change to bash-completion.eclass:

-RDEPEND="bash-completion?
-   ( || (
-   app-admin/eselect
-   app-shells/bash-completion-config
-   )
-   )"
+RDEPEND="bash-completion? ( app-admin/eselect )"

We should only be using eselect now to enable bash-completion. I think
bash-completion-config is broken now anyway
(https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this
change, I will p.mask b-c-c for removal.

Any concerns? The upgrade path in the future is going to be wierd as
upstream is releasing v1.0 soon, but that is not concern for now.
Thanks,
Jeremy