Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#38563 closed defect (fixed)

lua-lpeg, lpeg: duplicate port

Reported by: ci42 Owned by: anddam (Andrea D'Amore)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: andremm@…
Port: lua-lpeg lpeg

Description

lua-lpeg and lpeg are ports for the same software. I would suggest that we remove one of them and mark it replaced_by the other one. I think we should keep lpeg as it is the older one.

Change History (5)

comment:1 Changed 11 years ago by anddam (Andrea D'Amore)

Status: newassigned

I see, I missed the existing port as I expected it to have "lua" in the port name, the same way python packages have 'py' and perl 5 packages have 'p5'.

For this reason I consistently used a lua-<name> pattern for lua packages and therefore I'd rather keep lua-lpeg than lpeg name.

comment:2 in reply to:  1 Changed 11 years ago by ci42

Replying to and.damore@…:

For this reason I consistently used a lua-<name> pattern for lua packages and therefore I'd rather keep lua-lpeg than lpeg name.

That's reasonable. Who will be the maintainer? I think andremm gets precedence as his port is the older one. Maybe both of you can be listed as maintainer.

@andremm: What do you think?

comment:3 Changed 11 years ago by andremm@…

I'm cool with two maintainers. I also agree that lua-lpeg is more consistent and should be the official package for lpeg.

I'm sorry, I did not realize this common pattern among perl and python when I created lpeg for lua.

Last edited 11 years ago by andremm@… (previous) (diff)

comment:4 Changed 11 years ago by anddam (Andrea D'Amore)

Resolution: fixed
Status: assignedclosed

Committed r104576, I kept myself as maintainer.

There's been a stealth update today so you see different checksums and dist_subdir, I merged a few minor things from the lua-lpeg portfile. I'm closing this ticket.

comment:5 Changed 11 years ago by anddam (Andrea D'Amore)

Summary: lua-lpeg, lpeg: dulplicate portlua-lpeg, lpeg: duplicate port
Note: See TracTickets for help on using tickets.