-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optionally mark locally installed versions #6
Comments
yep, we spoke about that before didn't we? |
My take on this is that we should simply add a customisation variable or two around
where, say,
This means the customisation is all up to the user and doesn't need additional logic in l3build to handle inserting conditional lines of code. |
To sort out plk/biblatex#374, we'll need to address code in the area of this issue and #40. I'm working on the |
is there "any" real use case of making this optional? I mean install really is always local, no? |
@FrankMittelbach I was thinking mainly that for some packages (e.g. |
@FrankMittelbach Hoping to work on this later on today: let me see what looks 'good'! |
I took a look at how we solved things for -- For auto-editing
local tagname = "v3.17"
local tagdate = os.date("%Y-%m-%d")
function checkinit_hook()
local file = unpackdir .. "/biblatex.sty"
local filename = basename(file)
local f = assert(io.open(file,"rb"))
local content = f:read("*all")
f:close()
-- Deal with Unix/Windows line endings
content = string.gsub(content .. (string.match(content,"\n$") and "" or "\n"),
"\r\n", "\n")
local updated_content = update_tag(filename,content,tagname,tagdate)
if content == updated_content then
return 0
else
local path = dirname(file)
ren(path,filename,filename .. ".bak")
f = assert(io.open(file,"w"))
-- Convert line ends back if required during write
-- Watch for the second return value!
f:write((string.gsub(updated_content,"\n",os_newline)))
f:close()
rm(path,filename .. ".bak")
end
cp("biblatex.sty",unpackdir,testdir)
return 0
end I think a similar hook would be the best plan: I'll look to add. |
It would be useful to have
install
also optionally applysetversion
so for example\listfiles
will clearly show that development versions are in use.The text was updated successfully, but these errors were encountered: