[Rule Guideline] Modify Rule 17 to account for same subdirectories in submissions

[lcn2]

Is there an existing issue for this?

• I have searched for existing issues and did not find anything like it

Which Rule and/or Guideline has a problem?

Rule 17.

You submission may have additional files, however the filenames of those additional files MUST:

Be less than 100 characters in length.

Match the regular expression: ^[0-9A-Za-z][0-9A-Za-z._+-]*$

As well as:

Filenames in your entry (that is, not including the files generated by the mkiocccentry(1) tool or the tools it or any other tool invokes) MUST:

Be less than 100 characters in length

NOT have a / (excluding the entry directory that the mkiocccentry(1) tool generates).

NOT contain a path component of: . (that is, with the exception of files generated by mkiocccentry(1) itself, it must have NO .).

NOT contain a path component of: .. (that is, NO ..).

Match the regular expression ^[0-9A-Za-z][0-9A-Za-z._+-]*$ (again, excluding files generated by mkiocccentry(1)).

What is wrong with the Rule and/or Guideline?

Rule 17 disallows sane subdirectories in submissions.

How do you recommend we fix the problem?

Once issue 1060 in the mkiocccentry repo is resolved, then Rule 17 should be modified accordingly.

Anything else?

No response

[xexyl]

Assign please.

I already have the mkiocccentry code updated. Now I am waiting on the function in jparse and then I can finish txzchk. I really will be going afk now! I have my right leg dangling out of my bed so that I have to.

Back later ... please do a pull request in jparse with that function you refer to as you have the idea in your head and I am not clear entirely what it should do. Thanks!

[lcn2]

P.S. In regards to @SirWumpus' idea of supplying a test suite with lots of files
, a FAQ and/or Guideline could be added to suggest that if an entry runs into the MAX_FILE_COUNT problems, the should turn a large set of files (such as some large test suite) into a tarball.

Such a tarball would be untarred some Makefile rule (say make test) AND then cleaned up via make clobber, restoring the entry to a sane number of files.

See GH-issuecomment-2567936096 in "the other repo".

[lcn2]

Status update

The code needed to implement this enhancement is being worked on in "the other repo" issue 1060.

Meanwhile we plan to modify the rules and update the guidelines and likely the FAQ to accompany the work being done in "the other repo" in the near future. So in this case the rules and guidelines will likely lead the work needed to implement. I.e., tools such as mkiocccentry(1), txzchk(1) and chkcentry(1) will need to be re-released to "catch up to" (as the expression goes) the rules and guidelines.

We are going to lead with modifying the rules and guidelines so that it becomes more clear what the change will become to the developers in "the other repo".

UPDATE 0

Stay tuned ..

P.s., Our goal is to have this issue, and the "the other repo" issue 1060 resolved and tested by mid-January, well ahead of the date when the contest is anticipated to open.

[xexyl]

P.S. In regards to @SirWumpus' idea of supplying a test suite with lots of files , a FAQ and/or Guideline could be added to suggest that if an entry runs into the MAX_FILE_COUNT problems, the should turn a large set of files (such as some large test suite) into a tarball.

Such a tarball would be untarred some Makefile rule (say make test) AND then cleaned up via make clobber, restoring the entry to a sane number of files.

See GH-issuecomment-2567936096 in "the other repo".

If you forgot .. there's actually a test suite. It was built in long ago. It does not need to be a tarball per se as there's the read as text file mode a part of the test suite. There are already lots of test files and indeed more would be added when this is done.

[xexyl]

P.S. In regards to @SirWumpus' idea of supplying a test suite with lots of files , a FAQ and/or Guideline could be added to suggest that if an entry runs into the MAX_FILE_COUNT problems, the should turn a large set of files (such as some large test suite) into a tarball.
Such a tarball would be untarred some Makefile rule (say make test) AND then cleaned up via make clobber, restoring the entry to a sane number of files.
See GH-issuecomment-2567936096 in "the other repo".

If you forgot .. there's actually a test suite. It was built in long ago. It does not need to be a tarball per se as there's the read as text file mode a part of the test suite. There are already lots of test files and indeed more would be added when this is done.

UPDATE 0

In fact it was one of the first things I did - so I could make sure it works okay (that and using the tarballs you provided).

[lcn2]

We believe we have addressed all of the current questions that still need answering at this time. If we've missed something or something else needs to be clarified, please ask again.