In the bin!Ok they are not needed!
Well , that'd one way to do it. For me if package Manager does not find it I will see what is missing in the Log window anyway.My 2 cents -- Save the depend files. They take up very little disk space, and if you ever want to migrate a specific VAR from one computer to another, it can be a handy extra reference point. Not all assets can be discovered from the Package Manager. If the author of the package does a good job, every required asset (regardless of whether VaM / Package Manager knows its URL) should be included in the file. Personally, after I build a package, I modify/fix the depend file to include additional information to make it more useful. Perhaps most creators don't do that though. IMMV.
Well , that'd one way to do it. For me if package Manager does not find it I will see what is missing in the Log window anyway.
I am bit confused, how depend.txt helps you obtain missing asset?True, but the Log Window won't tell you where that asset was obtained. For most VARs it's a non-issue, but some assets can be hard to track down again.
I am bit confused, how depend.txt helps you obtain missing asset?
(if promo-link is not provided, asset is just bundled in/not original reference, or not packaged at all)
All you get is creatorName.packageName.Version (most of the time), same info is already provided elsewere.
Gotcha! abbreviation and acronyms (Your Mileage May Vary). ?As I eluded to earlier, I modify the depend file to contain actual direct links to each piece of dependency content. I'm guessing a lot of creators don't take the time to do that though, which is why I also said "YMMV".
Gotcha! abbreviation and acronyms (Your Mileage May Vary). ?
I just wanted to clarify that there isn't something i missed (looking from general use case),
but now i get it, that's your ('custom') use case.
on side note: wtf is IMMV?