kill set-wrap?

17 views
Skip to first unread message

Sebastien Lambla

unread,
May 16, 2012, 5:53:39 PM5/16/12
to openevery...@googlegroups.com

Hi all,

 

There’s something that’s nagging me a bit with the set-wrap command. The typical workflow is to change your dependency, which should then update the wraps based on the new stuff.

 

So you’d end up with set-wrap –version 2.1 –pre, then doing an update-wrap (that’s what we currently have).

 

Would everyone be comfortable with merging set-wrap into update-wrap, so you’d just use “update-wrap –version 2.1 –pre”? Is anyone acutally using set-wrap at all?

 

 

Ruben Vandeginste

unread,
May 21, 2012, 7:17:10 AM5/21/12
to openevery...@googlegroups.com
Sebastien,

To be honest, I probably never used the command set-wrap. I always
open the wrapdesc in an editor, or in visual studio and fix or add
dependencies in there. After changing it, I do an update-wrap on the
commandline. No objections from me... but I'll probably keep on doing
what I've gotten used to now. :)

Ruben

Sebastien Lambla

unread,
May 21, 2012, 9:47:00 AM5/21/12
to openevery...@googlegroups.com
I think that's what everyone has been using.

I'll merge the two commands then in a new update-wrap, that can either update to existing specs or change the specs for a specific package, and then do the update.

It's especially important with edge packages, as upgrading from nhibernate release to nhibernate beta would be otherwise rather cumbersome.

O update-wrap nhibernate -edge -version 3.4

Would generate "depends: nhibernate ~> 3.4 edge"

Upgrade to the release version would always work, but switching back to prod would be

o update-wrap nhibernate -release -version 3.4

I think I'm happier with this, and that's one less command to deal with for updating packages.

Seb
-----Original Message-----
From: openevery...@googlegroups.com [mailto:openevery...@googlegroups.com] On Behalf Of Ruben Vandeginste
Sent: 21 May 2012 12:17
To: openevery...@googlegroups.com
Subject: Re: [openeverything] kill set-wrap?

Sebastien,

To be honest, I probably never used the command set-wrap. I always open the wrapdesc in an editor, or in visual studio and fix or add dependencies in there. After changing it, I do an update-wrap on the commandline. No objections from me... but I'll probably keep on doing what I've gotten used to now. :)

Ruben

On Wed, May 16, 2012 at 11:53 PM, Sebastien Lambla <s...@serialseb.com> wrote:
> Hi all,
>
> There's something that's nagging me a bit with the set-wrap command.
> The typical workflow is to change your dependency, which should then
> update the wraps based on the new stuff.
>
> So you'd end up with set-wrap -version 2.1 -pre, then doing an
> update-wrap (that's what we currently have).
>
> Would everyone be comfortable with merging set-wrap into update-wrap,
> so you'd just use "update-wrap -version 2.1 -pre"? Is anyone acutally
> using set-wrap at all?
>
Reply all
Reply to author
Forward
0 new messages