Opened 16 years ago

Closed 7 years ago

#15484 closed defect (wontfix)

post-commit lint script should handle Portfiles anywhere in repository

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: server/hosting Version: 1.6.0
Keywords: Cc: drkp (Dan Ports)
Port:

Description

If I commit changes to a Portfile in trunk/dports/*/* a script runs which checks the Portfile syntax and emails any errors to the committer and maintainer. But if I have a Portfile elsewhere in the repository, such as under users/*/*, then the script emails me an error instead:

Portfile: pure-devel

Error: Unable to open port: Could not find Portfile in /tmp/mp_lint/36446/ryandesign/pure-devel

trunk/dports seems to be hardcoded into the script. But the script should support Portfiles, wherever in the repository they may be.

William said he doesn't have time to look into this right now so I may take a look.

Change History (9)

comment:1 Changed 15 years ago by wsiegrist@…

Owner: changed from wsiegrist@… to ryandesign@…

I've modified the lint script on the server. Please verify this is fixed next time you touch a Portfile outside of trunk/dports?

comment:2 Changed 15 years ago by raimue (Rainer Müller)

Milestone: Website & Documentation

comment:3 Changed 15 years ago by (none)

Milestone: Website & Documentation

Milestone Website & Documentation deleted

comment:4 Changed 15 years ago by raimue (Rainer Müller)

Resolution: fixed
Status: newclosed

It works for me correctly when committing to my /users/raimue/ports directory, so I consider this fixed.

comment:5 Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: closedreopened

You have directories in your ports directory for categories. I don't, because I don't need them.

comment:6 Changed 14 years ago by drkp (Dan Ports)

Cc: dports@… added

I'm not sure it should run lint on portfiles not in trunk/dports at all.

r68605 just got me 84 lint report emails, mostly telling me that a portgroup file or dependency couldn't be located. No surprise, they're only in my users directory, and I don't really expect it to look there, but I'd rather not be flooded by emails when it doesn't find them...

comment:7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

So... you're saying the server is now running lint on Portfiles not in trunk/dports? So... this ticket has been resolved?

To prevent the errors about the missing portgroup, feel free to put the new portgroup into the public tree already, even if it isn't quite done yet.

comment:8 in reply to:  7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to ryandesign@…:

So... you're saying the server is now running lint on Portfiles not in trunk/dports? So... this ticket has been resolved?

Oh, wait, I see, you too have category directories whereas I didn't. At the time I filed this ticket, it hadn't occurred to me to create category directories in my user directory. I suppose we could just officially recommend that people use category directories for ports in their user directory (if we don't already) and be done with it.

comment:9 Changed 7 years ago by raimue (Rainer Müller)

Resolution: wontfix
Status: reopenedclosed

We are no longer using Subversion, so I consider this to be no longer relevant. If someone wants a new lint job for the Git repository, that would be a separate issue.

Note: See TracTickets for help on using tickets.