./doc/build_docs for Epetra

[nschloe]

The most common way for a Trilinos package to build its docs is to call ./doc/build_docs. Unfortunately, Epetra doesn't have that, meaning that the Debian package, for example, doesn't contain Epetra docs. We've recently had a user point that out, so I thought I mention it here, hoping for someone to put a ./doc/build_docs in Epetra.

[mhoemmen]

@trilinos/epetra

[ibaned]

@trilinos/epetra isn't a team... @trilinos/framework someone needs to determine ownership of Epetra and create the @trilinos/epetra team...

[jwillenbring]

@nschloe what version are you looking at? I see such a file in the repo: https://github.com/trilinos/Trilinos/blob/master/packages/epetra/doc/build_docs

We rely on this for the official deoxygenated generation for the website.

[nschloe]

Thanks @jwillenbring for the reply.

I looked at the 12.10.1 release where you'll find

$ ls -l packages/epetra/
browser
cmake
CMakeLists.txt
Copyright.txt
example
ReleaseNotes.txt
src
test

– no docs/. They are in master however. Those files don't get filtered out in the release process, do they?

[bmpersc]

@nschloe Epetra does have an exclusion for the doc directory for the tarball release. It should still be there on the 12.10 branch, but not in the tarball(s) made from that branch.

I'm not sure what the specific reason for that exclusion was/is, but it could have been that there were documents that hadn't gone through the appropriate review process. Given that we are now releasing it as part of our repo those reviews should have already happened and would allow us to stop excluding that directory from the tarball. Is Epetra the only package this is an issue for or just the only one that has been noticed? I would suspect there are others.

[nschloe]

I would suspect there are others.

I guess there'll be others, but people don't really look at locally installed documentation anymore. Frankly I was surprised that the lack of Epetra (of all packages) got noticed at all. If that could be fixed for the next release, I could close the bug on the Debian side.

[mhoemmen]

I made an Epetra team: @trilinos/epetra

[github-actions]

This issue has had no activity for 365 days and is marked for closure. It will be closed after an additional 30 days of inactivity.
If you would like to keep this issue open please add a comment and remove the MARKED_FOR_CLOSURE label.
If this issue should be kept open even with no activity beyond the time limits you can add the label DO_NOT_AUTOCLOSE.

[github-actions]

This issue was closed due to inactivity for 395 days.