Jump to content
NATE

referencing a package in SVN

Recommended Posts

I want to put a link on our internal wiki page that points to a package in SVN but automatically calls VIPM to open this package and ask they user if they want to install it. Essentially I want to do something like this:

vipm://https://<repo/path>/<packagename>.vip

 

Is there a syntax for doing this?

Share this post


Link to post
Share on other sites

I want to put a link on our internal wiki page that points to a package in SVN but automatically calls VIPM to open this package and ask they user if they want to install it. Essentially I want to do something like this:

vipm://https:///.vip

 

Is there a syntax for doing this?

 

 

Hi Nate,

 

The following could work:

 

1) Create a VIPM repository on your local computer's hard drive.

 

2) Commit this local repository into SVN (e.g. http://server/svn/trunk/my_package_rep)

 

3) Have clients connect to the repository at it's Repo URL (e.g. http://server/svn/trunk/my_package_rep) -- note that this requires clients have VIPM Professional.

 

Also, you might want to check out the VIPM Repository Theory of Operation document for more info.

 

Please let me know if you have other questions or suggestions for ways to improve VIPM (you can also post these to the VIPM Idea Exchange)

 

-Jim

Share this post


Link to post
Share on other sites

Thanks for the quick reply Jim. Unfortunately we don't have many Pro licenses, and I'd rather not create a repository for something that I think should be an allowable ad hoc operation. We have different teams using different SVN repos, and on occasion its nice to share useful developer enhancement packages (like Quickdrop plugins), without having to put them into a shared VIPM repo and having all clients point to the shared repo (with a license they don't have).

 

Instead they should be able to just send out an email with a hyperlink, or put the hyperlink in a wiki page, and have a single click pull it up on VIPM.

 

Sounds like this is not currently possible, shame... Not too big of a problem, just requires downloading the package locally first, then double clicking locally. I was hoping there was a simple way to skip that step.

 

Nate

Share this post


Link to post
Share on other sites

Thanks for the quick reply Jim. Unfortunately we don't have many Pro licenses, and I'd rather not create a repository for something that I think should be an allowable ad hoc operation. We have different teams using different SVN repos, and on occasion its nice to share useful developer enhancement packages (like Quickdrop plugins), without having to put them into a shared VIPM repo and having all clients point to the shared repo (with a license they don't have).

 

Instead they should be able to just send out an email with a hyperlink, or put the hyperlink in a wiki page, and have a single click pull it up on VIPM.

 

Sounds like this is not currently possible, shame... Not too big of a problem, just requires downloading the package locally first, then double clicking locally. I was hoping there was a simple way to skip that step.

 

Nate

 

Hi Nate,

 

I agree that the feature you're describing would be nice for your use case, to avoid having to download the package file in the web browser. We're actively looking at ways to improve the package sharing user experience and will keep your suggestions and use case in mind.

 

Thanks for taking the time to provide your feedback and input!

 

-Jim

Share this post


Link to post
Share on other sites

Built packages that are "keepers" get stored in SVN along with their source. You could argue that's a silly thing to do, but it's a convenient way to make sure that version of the package never disappears in case you need it for antiquity.

 

We don't have a UNC method of accessing our SVN repo that we know of, no shadow copy is being generated.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.