Neil Bothwick wrote:
> On Mon, 2 Sep 2019 20:13:03 -0500, Dale wrote:
>
>>> This appears to be a non-default setting in Krusader. I just tried
>>> created text files, both as a user and as root, and they had 644
>>> permissions. For some reason, your Krusader is ignoring the umask
>>> setting and
On Mon, 2 Sep 2019 20:13:03 -0500, Dale wrote:
> > This appears to be a non-default setting in Krusader. I just tried
> > created text files, both as a user and as root, and they had 644
> > permissions. For some reason, your Krusader is ignoring the umask
> > setting and creating files with
Neil Bothwick wrote:
> On Mon, 2 Sep 2019 10:23:15 -0500, Dale wrote:
>
>> It appears Konsole creates a world readable file while Krusader
>> doesn't. To be honest tho, I sort of think Krusader is doing it
>> correctly. It does mean I have to change it for portage to work but it
>> should be set
On Mon, 2 Sep 2019 10:23:15 -0500, Dale wrote:
> It appears Konsole creates a world readable file while Krusader
> doesn't. To be honest tho, I sort of think Krusader is doing it
> correctly. It does mean I have to change it for portage to work but it
> should be set to portage since it is what
Arve Barsnes wrote:
> On Mon, 2 Sep 2019 at 11:28, Dale wrote:
>> It does it every time here. It did it just the other day. In the error
>> emerge spits out, it even says something about permissions and that's
>> when I remember to go change it. After that, it works fine. Maybe it
>> is not
On Mon, 2 Sep 2019 at 11:28, Dale wrote:
> It does it every time here. It did it just the other day. In the error
> emerge spits out, it even says something about permissions and that's
> when I remember to go change it. After that, it works fine. Maybe it
> is not world readable or
Neil Bothwick wrote:
> On Mon, 2 Sep 2019 03:36:42 -0500, Dale wrote:
>
>> I've used it a few times myself and it does work well. The only thing I
>> seem to always forget, until emerge pukes on my keyboard and reminds me,
>> file permissions need to be portage:portage. When I create the patch
On Mon, 2 Sep 2019 03:36:42 -0500, Dale wrote:
> I've used it a few times myself and it does work well. The only thing I
> seem to always forget, until emerge pukes on my keyboard and reminds me,
> file permissions need to be portage:portage. When I create the patch
> file, it is set to
Raffaele Belardi wrote:
> For those who had missed the news like myself:
>
> https://wiki.gentoo.org/wiki//etc/portage/patches
>
> I used it to patch two packages (gnucash and blender), works perfectly!
>
> raffaele
>
>
I've used it a few times myself and it does work well. The only thing I
seem
For those who had missed the news like myself:
https://wiki.gentoo.org/wiki//etc/portage/patches
I used it to patch two packages (gnucash and blender), works perfectly!
raffaele
Some packages can apply patches from /etc/portage/patches/, other don't.
Why don't all packages do that? Is there a way to make all packages
use /etc/portage/patches?
On 9/12/11 3:21 PM, Nikos Chantziaras wrote:
Some packages can apply patches from /etc/portage/patches/, other don't.
Why don't all packages do that? Is there a way to make all packages
use /etc/portage/patches?
It a specific function which needs to be added to the ebuild by the
writer.
12 matches
Mail list logo
