Dan McGee wrote:
On Tue, Jan 19, 2010 at 11:51 PM, Allan McRae wrote:
Dan McGee wrote:
On Tue, Jan 19, 2010 at 11:25 PM, Dan McGee wrote:
It was noted in FS#17533 that setgid bits are carried down into any
created
subdirectories, and thus could end up being in a built package if the
original
On Tue, Jan 19, 2010 at 11:51 PM, Allan McRae wrote:
> Dan McGee wrote:
>>
>> On Tue, Jan 19, 2010 at 11:25 PM, Dan McGee wrote:
>>>
>>> It was noted in FS#17533 that setgid bits are carried down into any
>>> created
>>> subdirectories, and thus could end up being in a built package if the
>>> or
Dan McGee wrote:
On Tue, Jan 19, 2010 at 11:25 PM, Dan McGee wrote:
It was noted in FS#17533 that setgid bits are carried down into any created
subdirectories, and thus could end up being in a built package if the
original package directory was marked g+s. When we create src/ and pkg/,
explicit
On Tue, Jan 19, 2010 at 11:25 PM, Dan McGee wrote:
> It was noted in FS#17533 that setgid bits are carried down into any created
> subdirectories, and thus could end up being in a built package if the
> original package directory was marked g+s. When we create src/ and pkg/,
> explicitly chmod the
It was noted in FS#17533 that setgid bits are carried down into any created
subdirectories, and thus could end up being in a built package if the
original package directory was marked g+s. When we create src/ and pkg/,
explicitly chmod them to remove any sticky bits.
Signed-off-by: Dan McGee
---
