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.

Sign up for GitHub

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

Jump to bottom

can we intelligently figure out which pkg has cached? #4

Closed
loceee opened this issue May 16, 2014 · 4 comments
Closed

can we intelligently figure out which pkg has cached? #4

loceee opened this issue May 16, 2014 · 4 comments
Assignees
@loceee
Labels
enhancement
Milestone
0.99

Comments

@loceee
Copy link
Contributor

loceee commented May 16, 2014

instead of manually telling junki.sh

suggest, find latest pkg by modification time in waiting room... that would have to be it and should be almost foolproof.
@loceee loceee mentioned this issue May 20, 2014
Closed
@loceee loceee self-assigned this May 20, 2014
@loceee loceee modified the milestones: 1.0, 0.99 May 20, 2014
@loceee
Copy link
Contributor Author

loceee commented May 21, 2014

ls -tr /Library/Application\ Support/JAMF/Waiting\ Room/ | tail -n 1 | grep -v .cache.xml

we shouldn't be parsing ls I know.. but if run directly after a pkg cache, and then check against patchoo's pkgdata metadata, we have a method to remove the manual passing of pkgname.

@loceee
Copy link
Contributor Author

loceee commented May 22, 2014

Built and committed to dev 27563c8

@loceee
Copy link
Contributor Author

loceee commented May 22, 2014

f093fb0 updated.. seems to work great!

@loceee
Copy link
Contributor Author

loceee commented May 28, 2014

merged into master 0.99! fe5936c

@loceee loceee closed this as completed May 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@loceee loceee

Labels
enhancement
Projects
None yet
Milestone
0.99
Development

No branches or pull requests
1 participant
@loceee