From sepen at crux-arm.nu  Thu Mar 22 13:27:02 2012
From: sepen at crux-arm.nu (Jose V Beneyto)
Date: Thu, 22 Mar 2012 14:27:02 +0100
Subject: [crux-devel] prt-get depupdate
Message-ID: <4F6B28A6.8000303@crux-arm.nu>

Hi,

I wrote a patch for prt-get that provides a new feature: 'depupdate'.
The purpose of this feature is to solve the problem of new deps in the 
update of a port.
An example of this could be a commit to gst-plugins-bad(*), which 
introduces new dependencies, so in
the case you only use the 'update' command, then you'll have an error 
due to new deps.

Bassically, 'depupdate' does the same like 'depinst' but with some 
differences:

[depinst foo]
   1. get dependencies of foo, and install missing ones
   2. install foo

[depupdate foo]
   1. get dependencies of foo, and install missing ones
   2. update foo

What to you think about?

Regards,

(*) 
http://crux.nu/gitweb/?p=ports/contrib.git;a=blobdiff;f=gst-plugins-bad/Pkgfile;h=8bd0245442effe3c70f090e75a4dec87061208c8;hp=fcc2d928047eb6d8b1230b046277f0628349ac16;hb=d2f05d05d444f2f55cff3187893b77191d0d9d44;hpb=e6eb7a216d7ceec2cddacb73b8545028ff5c6f47

-- 
Jose V Beneyto | http://sepen.it.cx/



From sepen at crux-arm.nu  Thu Mar 22 13:31:22 2012
From: sepen at crux-arm.nu (Jose V Beneyto)
Date: Thu, 22 Mar 2012 14:31:22 +0100
Subject: [crux-devel] prt-get depupdate
In-Reply-To: <4F6B28A6.8000303@crux-arm.nu>
References: <4F6B28A6.8000303@crux-arm.nu>
Message-ID: <4F6B29AA.9040803@crux-arm.nu>

On 03/22/12 14:27, Jose V Beneyto wrote:
> Hi,
>
> I wrote a patch for prt-get that provides a new feature: 'depupdate'.
sorry, I forgot to attach the patch

-- 
Jose V Beneyto | http://sepen.it.cx/


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: depupdate.diff
URL: <http://lists.crux.nu/pipermail/crux-devel/attachments/20120322/bb9275ad/attachment.ksh>

From fredrik at rinnestam.se  Thu Mar 22 13:38:16 2012
From: fredrik at rinnestam.se (Fredrik Rinnestam)
Date: Thu, 22 Mar 2012 14:38:16 +0100
Subject: [crux-devel] prt-get depupdate
In-Reply-To: <4F6B28A6.8000303@crux-arm.nu>
References: <4F6B28A6.8000303@crux-arm.nu>
Message-ID: <20120322133815.GA27820@zoidberg.obra.se>

On Thu, Mar 22, 2012 at 02:27:02PM +0100, Jose V Beneyto wrote:
> Hi,
> 
> I wrote a patch for prt-get that provides a new feature: 'depupdate'.
> The purpose of this feature is to solve the problem of new deps in
> the update of a port.
> An example of this could be a commit to gst-plugins-bad(*), which
> introduces new dependencies, so in
> the case you only use the 'update' command, then you'll have an
> error due to new deps.
> 
> Bassically, 'depupdate' does the same like 'depinst' but with some
> differences:
> 
> [depinst foo]
>   1. get dependencies of foo, and install missing ones
>   2. install foo
> 
> [depupdate foo]
>   1. get dependencies of foo, and install missing ones
>   2. update foo
> 
> What to you think about?
> 

Love it, good work!

-- 

Fredrik Rinnestam


From benisty.e at gmail.com  Thu Mar 22 14:41:50 2012
From: benisty.e at gmail.com (Emmanuel Benisty)
Date: Thu, 22 Mar 2012 21:41:50 +0700
Subject: [crux-devel] prt-get depupdate
In-Reply-To: <4F6B28A6.8000303@crux-arm.nu>
References: <4F6B28A6.8000303@crux-arm.nu>
Message-ID: <CA+i8gKJCK4j8XssTKsaoPmK1P16GpMJn6Bs=sXcdwwKPdH1Mvw@mail.gmail.com>

Hi,

On Thu, Mar 22, 2012 at 8:27 PM, Jose V Beneyto <sepen at crux-arm.nu> wrote:
> I wrote a patch for prt-get that provides a new feature: 'depupdate'.
> The purpose of this feature is to solve the problem of new deps in the
> update of a port.
>
> What to you think about?

Definitely very useful. Does it mean we could depsysup too?

Thanks.
-- Emmanuel


From jw at smts.ch  Thu Mar 22 16:13:01 2012
From: jw at smts.ch (Johannes Winkelmann)
Date: Thu, 22 Mar 2012 17:13:01 +0100
Subject: [crux-devel] prt-get depupdate
In-Reply-To: <CA+i8gKJCK4j8XssTKsaoPmK1P16GpMJn6Bs=sXcdwwKPdH1Mvw@mail.gmail.com>
References: <4F6B28A6.8000303@crux-arm.nu>
	<CA+i8gKJCK4j8XssTKsaoPmK1P16GpMJn6Bs=sXcdwwKPdH1Mvw@mail.gmail.com>
Message-ID: <CAEYbzYtHv22_qo1A_e3eK80aKmgcL8_B3U4RTbgZ69cggchB=g@mail.gmail.com>

Hi,

On Thu, Mar 22, 2012 at 3:41 PM, Emmanuel Benisty <benisty.e at gmail.com> wrote:
> Hi,
>
> On Thu, Mar 22, 2012 at 8:27 PM, Jose V Beneyto <sepen at crux-arm.nu> wrote:
>> I wrote a patch for prt-get that provides a new feature: 'depupdate'.
>> The purpose of this feature is to solve the problem of new deps in the
>> update of a port.
looks good. Nitpick: the output in the end will print a list of
packages which were "updated", where as some were actually newly
installed.

> Definitely very useful. Does it mean we could depsysup too?
The problem here is that this would potentially install dependencies a
user omitted on purpose before, since that's not tracked (in other
words prt-get can't decide whether something is really a new
dependency). I don't know whether users still do this, but it used to
be the case before. That said, if there's both sysup and depsysup I
guess it might be okay.

By the way: I wanted to rewrite the commands to look like this:
  install [--with-deps|--no-deps]
  update [--with-deps|--no-deps]
  sysup [--with-deps|--no-deps]
with corresponding options for prt-get.conf, so a user can choose
whether he/she wants manual control over dependencies or fully
automatic handling, with the option do disable it on a per command
basis. Before introducing both new depupdate and depsysup commands,
I'd suggest considering rewriting the interface to this :).

Best, Johannes
-- 
Johannes Winkelmann
jw at smts.ch


From benisty.e at gmail.com  Thu Mar 22 16:42:59 2012
From: benisty.e at gmail.com (Emmanuel Benisty)
Date: Thu, 22 Mar 2012 23:42:59 +0700
Subject: [crux-devel] prt-get depupdate
In-Reply-To: <CAEYbzYtHv22_qo1A_e3eK80aKmgcL8_B3U4RTbgZ69cggchB=g@mail.gmail.com>
References: <4F6B28A6.8000303@crux-arm.nu>
	<CA+i8gKJCK4j8XssTKsaoPmK1P16GpMJn6Bs=sXcdwwKPdH1Mvw@mail.gmail.com>
	<CAEYbzYtHv22_qo1A_e3eK80aKmgcL8_B3U4RTbgZ69cggchB=g@mail.gmail.com>
Message-ID: <CA+i8gK+UL69Ws8GYuqc+gveNV1_=CwTe3KZMbX3HmV6NP747TQ@mail.gmail.com>

On Thu, Mar 22, 2012 at 11:13 PM, Johannes Winkelmann <jw at smts.ch> wrote:
> Hi,
>
> On Thu, Mar 22, 2012 at 3:41 PM, Emmanuel Benisty <benisty.e at gmail.com> wrote:
>> Hi,
>>
>> On Thu, Mar 22, 2012 at 8:27 PM, Jose V Beneyto <sepen at crux-arm.nu> wrote:
>>> I wrote a patch for prt-get that provides a new feature: 'depupdate'.
>>> The purpose of this feature is to solve the problem of new deps in the
>>> update of a port.
> looks good. Nitpick: the output in the end will print a list of
> packages which were "updated", where as some were actually newly
> installed.
>
>> Definitely very useful. Does it mean we could depsysup too?
> The problem here is that this would potentially install dependencies a
> user omitted on purpose before, since that's not tracked (in other
> words prt-get can't decide whether something is really a new
> dependency). I don't know whether users still do this, but it used to
> be the case before. That said, if there's both sysup and depsysup I
> guess it might be okay.

DISCLAIMER: we all use CRUX our own way so what is true for me may be
wrong for you.

When I'm modifying a port to remove a dep I would lock the port to
avoid this kind of things to happen.
In fact, I believe that only depsysup is really useful, depupgrade
means you're already aware of the new dep, you could just
remove/depinst. With depsysup, even if you're not on #crux on did not
follow crux{,-devel}-ml, you're sure you won't miss it.