On 9/20/13 12:24 PM, Diego Elio Pettenò wrote:
> As Michał said.
Please consider updating the documentation - ebuild(5):
> RESTRICT = [strip,mirror,fetch,userpriv]
>This should be a space delimited list of portage features to
>restrict. You may use conditional syntax to vary re
Justin (jlec) posted on Fri, 20 Sep 2013 19:58:51 +0200 as excerpted:
> what is your opinion to set
>
> FEATURES="binchecks strip"
>
> for all those packages which purely install files. For example python
> package only installing scripts, or perl packages or latex. There might
> be more.
In ad
Dnia 2013-09-20, o godz. 19:58:51
"Justin (jlec)" napisał(a):
> what is your opinion to set
>
> FEATURES="binchecks strip"
>
> for all those packages which purely install files. For example python
> package only installing scripts, or perl packages or latex. There might
> be more.
Not worth th
On Fri, Sep 20, 2013 at 10:58 AM, Justin (jlec) wrote:
> what is your opinion to set
>
> FEATURES="binchecks strip"
>
> for all those packages which purely install files. For example python
> package only installing scripts, or perl packages or latex. There might
> be more.
It may help to describ
As Michał said.
Diego Elio Pettenò — Flameeyes
flamee...@flameeyes.eu — http://blog.flameeyes.eu/
On Fri, Sep 20, 2013 at 7:52 PM, Michał Górny wrote:
> Dnia 2013-09-20, o godz. 19:58:51
> "Justin (jlec)" napisał(a):
>
> > what is your opinion to set
> >
> > FEATURES="binchecks strip"
> >
> >
Hi,
what is your opinion to set
FEATURES="binchecks strip"
for all those packages which purely install files. For example python
package only installing scripts, or perl packages or latex. There might
be more.
Justin
signature.asc
Description: OpenPGP digital signature
On 9/15/13 10:01 AM, William Hubbs wrote:
> All,
>
> here is another question wrt OpenRC's api.
>
> Currently we store two header files (rc.h and einfo.h) in /usr/include.
> Since we have more than one include file, wouldn't it be standard
> practice to store them in a sub directory of /usr/inclu
On 9/20/13 9:27 AM, Michał Górny wrote:
> Putting another includedir is even worse kind of band-aid. If we're to
> put them in a directory, I'd rather require 'more complete' includes,
> like:
>
> #include
>
> Otherwise, you're just fighting conflicts in the scope of a single
> application.
E
Dnia 2013-09-20, o godz. 18:12:17
Peter Stuge napisał(a):
> "Paweł Hajdan, Jr." wrote:
> > Also, it may be easier to change now when we only have two headers,
> > than later. And you may even add compatibility symlinks or copies in
> > /usr/include to give people more time to update.
>
> I think
"Paweł Hajdan, Jr." wrote:
> Also, it may be easier to change now when we only have two headers,
> than later. And you may even add compatibility symlinks or copies in
> /usr/include to give people more time to update.
I think you should rip off the band-aid quickly.
Move the files and update the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Oops, didn't follow proper removal procedure; reset the counter on
this one.
# Ian Stakenvicius (20 Sep 2013)
# on behalf of mozi...@gentoo.org
# Severely outdated, no interest in maintaining,
# only a matter of time before it breaks,
# major QA is
On 09/19/2013 04:00 PM, justin wrote:
Hi all,
I like to announce the newest addition from Russia to out dev team,
Heather Cynede (cynede).
It's the long awaited addition to the dotnet and haskell team, where
there are already a couple of the contribution. The Gamerlay Overlay
also got commits.
12 matches
Mail list logo
