Skip to content
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

pkj review from clone assumes dist goes into target #43

Closed
cbm755 opened this issue Mar 25, 2019 · 9 comments
Closed

pkj review from clone assumes dist goes into target #43

cbm755 opened this issue Mar 25, 2019 · 9 comments

Comments

@cbm755
Copy link

cbm755 commented Mar 25, 2019

Should make dist put things into target/foo.tar.gz? Doctest and Symbolic both use tmp/ but of course I could change that if target is somehow the standard place...

@apjanke
Copy link
Owner

apjanke commented Mar 25, 2019

I don't know enough about the Forge packaging conventions to know if there is a standard place, but target is the place I've seen a few packages put it, so that's where I assumed it should go.

I think a standard place will have to be required if we're going to make the release process more automated. Shall we adopt target since some packages are already using it?

@cbm755
Copy link
Author

cbm755 commented Mar 25, 2019

I would be fine with whatever but target isn't meaningful to me personally.. @mtmiller any input on this?

@mtmiller
Copy link
Contributor

I find that surprising and would much rather that make dist put foo.tar.gz in the current directory.

@cbm755
Copy link
Author

cbm755 commented Mar 25, 2019

That certainly sounds better than tmp! @apjanke: maybe pkj should allow { '/', '/target', '/tmp', ...} but all are deprecated except / and we'll slowly get everyone on board?

Can you make it warn('found foo in target/foo.tar.gz: this is deprecated, suggest moving dist file to root')?

@cbm755
Copy link
Author

cbm755 commented Mar 25, 2019

Its always annoyed me that foo-html.tar.gz isn't versioned: we should change that convention!

@apjanke
Copy link
Owner

apjanke commented Mar 25, 2019

Yes, yes, and yes. I'll add this later today.

@cbm755
Copy link
Author

cbm755 commented Mar 25, 2019

I like the idea of pkj nudging us all toward a standard: "be firm and verbose but forgiving".

@apjanke
Copy link
Owner

apjanke commented Mar 25, 2019

I'll expand it to have the notion of warnings in addition to outright failures.

@apjanke
Copy link
Owner

apjanke commented Mar 25, 2019

Done in 8fc6edb.

octave:18> pwd
ans = /Users/janke/tmp/octave-forge/repos/octave-doctest
octave:19> pkj review .
tar: Option --mtime=2019-03-23 12:31:42 -0300 is not supported
Usage:
  List:    tar -tf <archive-filename>
  Extract: tar -xf <archive-filename>
  Create:  tar -cf <archive-filename> [filenames...]
  Help:    tar --help
Package review failed for ..
Errors:
    Distribution tarball was empty
Warnings:
    Expected dist file doctest-0.7.0.tar.gz not created by 'make dist' in root of repo
  Actual dist file was at tmp/doctest-0.7.0.tar.gz
octave:20>

These errors are due to gnu-octave/octave-doctest#216.

@apjanke apjanke closed this as completed Mar 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants