Carlos Silva posted on Thu, 25 Apr 2013 22:51:01 + as excerpted:
> gentoo *running* in a box without it having network connection
> [is AFAIK] not something any John Doe would do. Offline
> installations and "runtimes" are for geeks that use linux for a long
> time and know how the system work
Hi!
On Thu, 25 Apr 2013, Steven J. Long wrote:
> Thanks, that sounds reasonable: one minor nitpick, though. Could you not
> call it 'stdnet'? Since from all the other discussion it appears like this
> is not going away soon for the vast majority of users, but simply being
> maintained as another
Hi!
On Wed, 24 Apr 2013, William Hubbs wrote:
> The primary disadvantages of newnet are that services can't depend on a
> single network interface, and it is not possible to stop/start a single
> interface.
Which is why it doesn;t work for my not-exactly-complex,
not-exactly-simple setup (NFS an
Hi!
On Fri, 26 Apr 2013, Tobias Klausmann wrote:
> I'm still not quite sure what newnet does that oldnet doesn't, or
> why somebody felt it was necessary to make a new package (and no,
> let's not discuss that here). Whatever it is, ideally, it would
> reflected in the name(s). And package descri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/04/13 01:49, Robin H. Johnson wrote:
> This is NOT intended to take oldnet away from OpenRC systems at
> all, but rather to encourage growth of both parts independently.
For what it's worth, I think this sounds reasonable. Especially
considerin
On Apr 26, 2013 4:59 AM, "Tobias Klausmann" wrote:
>
> Hi!
>
> On Fri, 26 Apr 2013, Tobias Klausmann wrote:
> > I'm still not quite sure what newnet does that oldnet doesn't, or
> > why somebody felt it was necessary to make a new package (and no,
> > let's not discuss that here). Whatever it is,
On 04/24/2013 06:16 PM, William Hubbs wrote:
> All,
>
> it has been suggested that gentoo's oldnet scripts be split out into
> their own package separate from OpenRC so that they can be developed
> independently. I am looking at doing this for OpenRC 0.12, which I hope
> to release soon.
>
> This
Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
other. I wonder if the former should imply the latter.
Is there any package where the files in SRC_URI cannot be mirrored
(i.e., redistributed), but where the built package can be distributed?
Ulrich
Ulrich Mueller wrote:
> Is there any package where the files in SRC_URI cannot be mirrored
> (i.e., redistributed), but where the built package can be distributed?
All of them, when distributing binaries within a legal entity.
//Peter
Michał Górny schrieb:
> On Mon, 22 Apr 2013 20:21:55 +0800
> Ben de Groot wrote:
>
>> On 22 April 2013 03:43, Michał Górny wrote:
>>
>>> The common kind of committed dep now looks like:
>>>
>>> || (
>>> (
>>> x11-libs/libXfoo[abi_x86_32]
>>> x11-libs/libXbar[abi_x86_32]
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2013 12:05 PM, Ulrich Mueller wrote:
> Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
> other. I wonder if the former should imply the latter.
>
> Is there any package where the files in SRC_URI cannot be mirrored
> (i
On Fri, 26 Apr 2013 07:20:39 -0400
Michael Mol wrote:
> On Apr 26, 2013 4:59 AM, "Tobias Klausmann"
> wrote:
> > On Fri, 26 Apr 2013, Tobias Klausmann wrote:
> > > I'm still not quite sure what newnet does that oldnet doesn't, or
> > > why somebody felt it was necessary to make a new package (an
On Fri, 26 Apr 2013 12:21:17 -0400
"Rick \"Zero_Chaos\" Farina" wrote:
> I agree with you entirely, but there is one major bit of information
> missing... What exactly does RESTRICT=bindist do? AFAICT it does
> exactly nothing. If we are going to address merging the two
> restriction (which I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2013 12:56 PM, Jeroen Roovers wrote:
> On Fri, 26 Apr 2013 12:21:17 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> I agree with you entirely, but there is one major bit of information
>> missing... What exactly does RESTRICT=bindist do? A
On Fri, 26 Apr 2013 13:14:07 -0400
"Rick \"Zero_Chaos\" Farina" wrote:
> Yes warnings are nice, but building a few thousand packages a day I
> honestly don't read all the warnings... I trust that when I tell
> portage/catalyst I am going to bindist that it would attempt to help
> keep me on the
Ulrich Mueller schrieb:
> Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
> other. I wonder if the former should imply the latter.
>
> Is there any package where the files in SRC_URI cannot be mirrored
> (i.e., redistributed), but where the built package can be distributed?
William Hubbs schrieb:
> if we keep a dependency for a while, even behind something like
> IUSE="+oldnet", when we drop it, people will still be hit if they
> do emerge --depclean before they emerge gentoo-oldnet.
In my opinion USE flags should toggle dependencies only in
metapackages or rare exce
On Fri, Apr 26, 2013 at 07:27:06PM +0200, Chí-Thanh Christopher Nguyễn wrote:
> William Hubbs schrieb:
> > if we keep a dependency for a while, even behind something like
> > IUSE="+oldnet", when we drop it, people will still be hit if they
> > do emerge --depclean before they emerge gentoo-oldnet.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/04/13 02:12 PM, Robin H. Johnson wrote:
> On Fri, Apr 26, 2013 at 07:27:06PM +0200, Chí-Thanh Christopher
> Nguyễn wrote:
>> William Hubbs schrieb:
>>> if we keep a dependency for a while, even behind something
>>> like IUSE="+oldnet", when we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2013 01:15 PM, Jeroen Roovers wrote:
> On Fri, 26 Apr 2013 13:14:07 -0400
> "Rick \"Zero_Chaos\" Farina" wrote:
>
>> Yes warnings are nice, but building a few thousand packages a day I
>> honestly don't read all the warnings... I trust that
On Fri, Apr 26, 2013 at 2:30 PM, Rick "Zero_Chaos" Farina
wrote:
> The user is distinguishing right from wrong by setting things like
> USE=bindist, portage simply doesn't seem to be respecting that in the
> case of RESTRICT=bindist.
I think what is missing is a clear set of definitions.
USE=-bi
On Friday 26 April 2013 12:05:10 Ulrich Mueller wrote:
> Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
> other. I wonder if the former should imply the latter.
>
> Is there any package where the files in SRC_URI cannot be mirrored
> (i.e., redistributed), but where the bui
On Fri, Apr 26, 2013 at 02:14:57PM -0400, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 26/04/13 02:12 PM, Robin H. Johnson wrote:
> > On Fri, Apr 26, 2013 at 07:27:06PM +0200, Chí-Thanh Christopher
> > Nguyễn wrote:
> >> William Hubbs schrieb:
> >>> if we keep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2013 02:44 PM, Rich Freeman wrote:
> On Fri, Apr 26, 2013 at 2:30 PM, Rick "Zero_Chaos" Farina
> wrote:
>> The user is distinguishing right from wrong by setting things like
>> USE=bindist, portage simply doesn't seem to be respecting that in
> On Fri, 26 Apr 2013, Mike Frysinger wrote:
>> Currently RESTRICT=mirror and RESTRICT=bindist are independent of
>> each other. I wonder if the former should imply the latter.
>>
>> Is there any package where the files in SRC_URI cannot be mirrored
>> (i.e., redistributed), but where the bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 26/04/13 03:07 PM, Rick "Zero_Chaos" Farina wrote:
> On 04/26/2013 02:44 PM, Rich Freeman wrote:
>> On Fri, Apr 26, 2013 at 2:30 PM, Rick "Zero_Chaos" Farina
>> wrote:
>>> The user is distinguishing right from wrong by setting things
>>> like US
On Fri, Apr 26, 2013 at 3:24 PM, Ian Stakenvicius wrote:
> IUSE="bindist" tends to be for adjusting a particular package so that
> it either is generic and CAN be binary-distributable, or will build as
> upstream intended (with, for instance, upstream branding) and
> therefore is not. Right?
Cor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/26/2013 03:24 PM, Ian Stakenvicius wrote:
> On 26/04/13 03:07 PM, Rick "Zero_Chaos" Farina wrote:
>> On 04/26/2013 02:44 PM, Rich Freeman wrote:
>>> On Fri, Apr 26, 2013 at 2:30 PM, Rick "Zero_Chaos" Farina
>>> wrote:
The user is distingui
On Fri, Apr 26, 2013 at 3:43 PM, Rick "Zero_Chaos" Farina
wrote:
> Based on Rich's suggestion my thought is have a new license group for
> things which are ALWAYS binary restricted, accepted by default, but
> removed from ACCEPT_LICENSE when USE=bindist. That is just what is
> rolling around in m
On 04/26/2013 09:23 PM, Ulrich Mueller wrote:
>> On Fri, 26 Apr 2013, Mike Frysinger wrote:
>
>>> Currently RESTRICT=mirror and RESTRICT=bindist are independent of
>>> each other. I wonder if the former should imply the latter.
>>>
>>> Is there any package where the files in SRC_URI cannot be
On Friday 26 April 2013 15:23:42 Ulrich Mueller wrote:
> > On Fri, 26 Apr 2013, Mike Frysinger wrote:
> >> Currently RESTRICT=mirror and RESTRICT=bindist are independent of
> >> each other. I wonder if the former should imply the latter.
> >>
> >> Is there any package where the files in SRC_UR
i've finally gotten off my butt and set up a new arm box for devs with hosting
by OSU. it's a wee bit faster than the armv4 netwinder :). it's an ARM
Samsung Chromebook which is dual core 1.7GHz and 2GB ram.
http://www.gentoo.org/proj/en/infrastructure/dev-machines.xml
-mike
signature.asc
Des
So years ago, we had GRP (the Gentoo Reference Platform.) My understanding
of USE=bindist was that when building packages whose binaries were illegal
to distribute, the build system would take some action. For instance, for a
while we were not allowed to brand a source build of firefox as firefox,
Chí-Thanh Christopher Nguyễn posted on Fri, 26 Apr 2013 19:19:32 +0200 as
excerpted:
> Ulrich Mueller schrieb:
>> Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
>> other. I wonder if the former should imply the latter.
>>
>> Is there any package where the files in SRC_URI c
Some ebuilds need to explicitly override bash-completion directory in
build system due to build systems having default non-matching Gentoo (or
rather Gentoo having bash-completion dir not matching anything else).
It's better to have a function to obtain that directory rather than for
ebuilds to ha
35 matches
Mail list logo
