On Wed, Aug 05, 2015 at 04:50:40AM +, Duncan wrote:
> Ian Stakenvicius posted on Tue, 04 Aug 2015 17:17:51 -0400 as excerpted:
>
> > So what you are suggesting here now is that you want to (A) potentially
> > break mounting with the need to externally manage mounts via services in
> > openrc i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/08/15 10:01 AM, William Hubbs wrote:
> On Wed, Aug 05, 2015 at 04:50:40AM +, Duncan wrote:
>> Ian Stakenvicius posted on Tue, 04 Aug 2015 17:17:51 -0400 as
>> excerpted:
>>
>>> So what you are suggesting here now is that you want to (A)
>>
On Wed, Aug 05, 2015 at 10:18:13AM -0400, Ian Stakenvicius wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 05/08/15 10:01 AM, William Hubbs wrote:
> > On Wed, Aug 05, 2015 at 04:50:40AM +, Duncan wrote:
> >> Ian Stakenvicius posted on Tue, 04 Aug 2015 17:17:51 -0400 as
> >> e
On Tue, Aug 04, 2015 at 02:19:52PM -0500, William Hubbs wrote:
> On Tue, Aug 04, 2015 at 12:17:50PM -0400, Mike Gilbert wrote:
> > The documentation says you are extracting to ${S}, but the function
> > actually extracts to ${WORKDIR}/${PN}.
>
> s/PN/P/
> > I would get rid of the useless "destdi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/08/15 02:38 AM, Ben de Groot wrote:
> On 4 August 2015 at 22:56, Ian Stakenvicius
> wrote:
>> Are there any cases where things actually break if a package has
>> both flags enabled? IE, is three a package with IUSE="qt4 qt5"
>> that when both
> "WH" == William Hubbs writes:
WH> The other change I want to make, considering that the mount.* scripts
WH> will actually do the work of mounting the file systems, is to turn
WH> localmount and netmount into wrappers which will do nothing other than
WH> pull in the appropriate mounts. The s
On Wed, Aug 5, 2015 at 8:09 PM, James Cloos wrote:
>> "WH" == William Hubbs writes:
> WH> What do folks think of these changes?
>
> For local filesystems, mount -a is exactly right and should remain. At
> least for those of us who prefer only ever halving to edit fstab(5).
> --
> James Cloos
William Hubbs posted on Wed, 05 Aug 2015 10:26:33 -0500 as excerpted:
> It isn't localmount that would have the issue, but mount.* because they
> are lexically after localmount, so you would end up with localmount
> doing a mount -a then mount.* coming later trying to mount file systems
> again th
