Base is not read-only

[3f6a]

julia> @edit LogExpFunctions.logaddexp(4, 5) # opened file is read-only (same happens for any other packages)

julia> @edit sin(4) # opened file is NOT read-only. Seems to occur for all base Julia installation files

Expected behavior: Base files should also be read-only. Seems permissions are not set correctly during installation?

I tested this on Mac (Apple silicon) and Linux (x86). In both cases I installed Julia via juliaup (just ran the script curl -fsSL https://install.julialang.org | sh).

julia> versioninfo()
Julia Version 1.9.3
Commit bed2cd540a1 (2023-08-24 14:43 UTC)
Build Info:
  Official https://julialang.org/ release
Platform Info:
  OS: macOS (arm64-apple-darwin22.4.0)
  CPU: 8 × Apple M2
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-14.0.6 (ORCJIT, apple-m1)
  Threads: 1 on 4 virtual cores
Environment:
  JULIA_EDITOR = mvim
  JULIA_PKG_USE_CLI_GIT = true
  JULIA_PKG_SERVER_REGISTRY_PREFERENCE = eager

[longemen3000]

i can reproduce in windows, 1.9.1

[StefanKarpinski]

I suppose that installing Julia as read-only would make sense. Should we change this in the build process or the install process?

[stevengj]

Seems like this should be a packaging/installer thing?

[spaette]

julia 1.9.3

bash-5.1$ ls -l /usr/share/julia/base/math.jl
-rw-r--r-- 1 root root 39979 Aug 25 00:37 /usr/share/julia/base/math.jl
bash-5.1$ 

an ordinary (non-root) user opening math.jl

1. in emacs in the echo buffer appears the message "Note: file is write protected"
2. in vim it is listed as [readonly]

---

update

LogExpFunctions v0.3.26

bash-5.1$ pushd ~/.julia/packages/LogExpFunctions/W8b4e/src             
~/.julia/packages/LogExpFunctions/W8b4e/src ~
bash-5.1$ ls -l basicfuns.jl
-r--r--r-- 1 soeren soeren 11905 Aug 26 15:12 basicfuns.jl
bash-5.1$ popd
~
bash-5.1$ 

[KristofferC]

I think that is more based on how you installed Julia. A standard installation will not have that property.

[3f6a]

It's a juliaup issue then?

[KristofferC]

No, the same applies to the official installation method.

[spaette]

julia> @edit sin(4)

I presume @3f6a was running julia as an ordinary user.

julia-1.9.3-linux-x86_64.tar.gz

I suppose unless modified math.jl will have read/write perms for the ordinary or root user who extracted the precompiled .tar.gz.

Possibly over then next weeks on S.u.S.E. Leap I can look at juliaup.

I've the following currently on SuSE Linux (version 15.4) which runs KDE as the graphical desktop.

bash-4.4$ curl -s https://julialang-s3.julialang.org/bin/linux/x64/1.9/julia-1.9.2-linux-x86_64.tar.gz \
> | tar -xz
bash-4.4$ ln -s ~/julia-1.9.2/bin/julia ~/bin/julia
bash-4.4$ mkdir -p ~/.local/share/{applications,icons/hicolor/48x48/apps}
bash-4.4$ curl -s -o ~/.local/share/icons/hicolor/48x48/apps/julia.png \
> https://raw.githubusercontent.com/JuliaLang/julia/master/contrib/julia.png
bash-4.4$ cp ~/julia-1.9.2/share/applications/julia.desktop ~/.local/share/applications
bash-4.4$ gzip -9 ~/julia-1.9.2/share/man/man1/julia.1
bash-4.4$ ln -s ~/julia-1.9.2/share/man/man1/julia.1.gz ~/.local/man/man1/julia.1.gz
bash-4.4$ 

---

update

As a test I uninstalled the above and ran juliaup's curl -fsSL https://install.julialang.org | sh.

The math.jl file has the identical read/write perms as in the direct .tar.gz download as extracted.

bash-4.4$ pushd ~/.julia/juliaup/julia-1.9.3+0.x64.linux.gnu/share/julia/base
~/.julia/juliaup/julia-1.9.3+0.x64.linux.gnu/share/julia/base ~
bash-4.4$ ls -l math.jl
-rw-r--r-- 1 soeren users 39979 Aug 24 10:36 math.jl
bash-4.4$ popd
~
bash-4.4$

Perms are the responsibility of the admin for a system installed program, or the user for a locally installed program.

[spaette]

read-only would make sense

packaging/installer thing

In the Un*x filesystem hierarchy standard /usr/share is for achitecture-independent data.

It's rather generic with Slackware Community submitted build scripts for source downloads to check perms.

SlackBuild Script Templates

$ ed -s autotools-template.SlackBuild <<<'110,114p'
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;
$ 

So one could add a shell script to precompiled julia downloads for non-root users to optionally run after local installs.

---

Of further note it's also rather generic to compress man pages.

$ ed -s autotools-template.SlackBuild <<<'145,150p'
# Compress man pages
# If the man pages are installed to /usr/share/man instead, you'll need to either
# add the --mandir=/usr/man flag to configure or move them manually after the
# make install process is run.
find $PKG/usr/man -type f -exec gzip -9 {} \;
for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done
$ 

[3f6a]

I presume @3f6a was running julia as an ordinary user.

Yes, I am.

By the way, also the stdlibs are not read-only:

julia> using Random: bitrand
julia> @edit bitrand(4) #  file is not opened as read-only. Same for all stdlib source files

[spaette]

Binary Installation

Perhaps a command changing perms for locally installed pre-compiled binaries could be added in the above section.

Julia developers might determine if any tree output listed subdirectories should be excluded from such command.

bash-4.4$ pushd ~/julia-1.9.2/share 
~/julia-1.9.2/share ~
bash-4.4$ tree -L 1 --noreport julia
julia
├── base
├── base.cache
├── cert.pem
├── compiled
├── julia-config.jl
├── stdlib
└── test
bash-4.41$ popd
~
bash-4.4$ 

---

The juliaup code could be modified to determine whether local or system installs are being performed and change perms on the former.

[spaette]

@ViralBShah

The directory ~/julia*/share/julia/compiled is unaffected by running the command.

Marking PR a Draft.

This is the current command submitted on the premise that none of the affected files need be writeable.

if [ -d ~/julia*/share/julia ]; then
  find ~/julia*/share/julia/{base,stdlib,test} -perm 644 -exec chmod 444 {} \;
fi

This would be more comprehensive, again under the premise that none of the affected files need be writeable.

if [ -d ~/julia*/share/julia ]; then
  find ~/julia*/share/julia \
    -perm 755 -exec chmod 555 {} \+ -o -perm 644 -exec chmod 444 {} \+
fi

[spaette]

@davidanthoff

As a juliaup Collaborator any opinion on this ticket and pull request?

[spaette]

@longemen3000

can reproduce in windows, 1.9.1

JULIA_EDITOR

$JULIA_EDITOR takes precedence over $VISUAL, which in turn takes precedence over $EDITOR. If none of these environment variables is set, then the editor is taken to be open on Windows and OS X, or /etc/alternatives/editor if it exists, or emacs otherwise.

I think PowerShell accepts either forward or back slashes in the PATH.

(Get-ChildItem julia-1.9.3/share/julia/base/math.jl).Set_IsReadOnly($True)

The above PowerShell command can be adapted as per julia version and the location of the math.jl file.

FWIW, Notepad.exe does not indicate to the user when a file is readonly.

---

@andyleejordan

Download
julia-1.9.3-win64.zip

Would you and/or the PowerShell Team be amenable to recommending a command to recursively change the *.jl files to readonly?

The extracted *.zip file's etc directory tree contains the startup.jl file which can be left unchanged.

On Windows one would replace UnixMode with Mode in the below.

The Windows download unlike the Generic Linux download includes a julia-config.jl file that is not executable.

---

FWIW, this will list the *.jl files under the *.zip file's base directory tree.

Get-ChildItem -Path julia-1.9.3/share/julia/base -Recurse -Filter *.jl