Re: Tracking commit messages from cli

2009-11-12 Thread Troels Kofoed Jacobsen
On Mon, Nov 09, 2009 at 05:55:57PM -0500, APseudoUtopia wrote:
 On Sun, Nov 8, 2009 at 2:06 PM, Troels Kofoed Jacobsen
 tkjacob...@gmail.com wrote:
  Hi all
 
  With pkg_version I can easily see which installed ports has newer
  versions available, but what I miss is a way to see what has changed.
  The reason for this is that commit messages often say that only the
  pkg-plist has changed or something that does not make me want to update.
 
  Right now I'm reading the commit messages from the cvs web frontend, but
  it would be awesome with a program that could say:
  gd-2.0.35_1,1    needs updating (index has 2.0.35_2,1)
  Commit messages between the versions:
  blah blah blah
  blah ... ...
  ...
 
  I know freshports exist, but I would rather not have to open a web
  browser.
 
  Does such a program exist or do I have to write my own. In the latter
  case can anyone point me to an easy way to get raw-text versions of
  commit messages without having to track the whole tree. Does freshports
  e.g. have an api -- it has all the necessary information, just not
  available in a suitable form (to my knowledge)
 
  Best regards
  Troels Kofoed Jacobsen
 
 I asked this question some time ago and never got a response. I
 currently just use a browser and visit www.freebsd.org/ports/ and read
 the commit log there. So far, I haven't found any other alternative.

If anyone's interested I've hacked together a small python script doing
this:
https://www.student.dtu.dk/~s052580/?page=software/commitmessages

Best regards
Troels Kofoed Jacobsen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Tracking commit messages from cli

2009-11-09 Thread APseudoUtopia
On Sun, Nov 8, 2009 at 2:06 PM, Troels Kofoed Jacobsen
tkjacob...@gmail.com wrote:
 Hi all

 With pkg_version I can easily see which installed ports has newer
 versions available, but what I miss is a way to see what has changed.
 The reason for this is that commit messages often say that only the
 pkg-plist has changed or something that does not make me want to update.

 Right now I'm reading the commit messages from the cvs web frontend, but
 it would be awesome with a program that could say:
 gd-2.0.35_1,1    needs updating (index has 2.0.35_2,1)
 Commit messages between the versions:
 blah blah blah
 blah ... ...
 ...

 I know freshports exist, but I would rather not have to open a web
 browser.

 Does such a program exist or do I have to write my own. In the latter
 case can anyone point me to an easy way to get raw-text versions of
 commit messages without having to track the whole tree. Does freshports
 e.g. have an api -- it has all the necessary information, just not
 available in a suitable form (to my knowledge)

 Best regards
 Troels Kofoed Jacobsen

I asked this question some time ago and never got a response. I
currently just use a browser and visit www.freebsd.org/ports/ and read
the commit log there. So far, I haven't found any other alternative.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Tracking commit messages from cli

2009-11-08 Thread Troels Kofoed Jacobsen
Hi all

With pkg_version I can easily see which installed ports has newer
versions available, but what I miss is a way to see what has changed.
The reason for this is that commit messages often say that only the
pkg-plist has changed or something that does not make me want to update. 

Right now I'm reading the commit messages from the cvs web frontend, but
it would be awesome with a program that could say:
gd-2.0.35_1,1needs updating (index has 2.0.35_2,1)
Commit messages between the versions:
blah blah blah
blah ... ... 
...

I know freshports exist, but I would rather not have to open a web
browser.

Does such a program exist or do I have to write my own. In the latter
case can anyone point me to an easy way to get raw-text versions of
commit messages without having to track the whole tree. Does freshports
e.g. have an api -- it has all the necessary information, just not
available in a suitable form (to my knowledge)

Best regards
Troels Kofoed Jacobsen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Tracking commit messages from cli

2009-11-08 Thread Roman Neuhauser
On Sun, Nov 08, 2009 at 08:06:13PM +0100, Troels Kofoed Jacobsen wrote:
 With pkg_version I can easily see which installed ports has newer
 versions available, but what I miss is a way to see what has changed.
 The reason for this is that commit messages often say that only the
 pkg-plist has changed or something that does not make me want to update. 

...

 I know freshports exist, but I would rather not have to open a web
 browser.
 
 Does such a program exist or do I have to write my own.

sorry to point out the obvious, but why not use svn (or cvs)?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Tracking commit messages from cli

2009-11-08 Thread Troels Kofoed Jacobsen
On Sun, Nov 8, 2009 at 11:26 PM, Roman Neuhauser neuhau...@sigpipe.cz wrote:
 On Sun, Nov 08, 2009 at 08:06:13PM +0100, Troels Kofoed Jacobsen wrote:
 With pkg_version I can easily see which installed ports has newer
 versions available, but what I miss is a way to see what has changed.
 The reason for this is that commit messages often say that only the
 pkg-plist has changed or something that does not make me want to update.

 ...

 I know freshports exist, but I would rather not have to open a web
 browser.

 Does such a program exist or do I have to write my own.

 sorry to point out the obvious, but why not use svn (or cvs)?


As I said: without having to track the whole tree. I know this would
be a possibility, but would rather not use the convenience of
portsnap. Also if the solution should be more usable for other people
I would like it to be as simple as possible and not require so much
overhead.

Anyway, thanks for the answer -- maybe I'll just do that eventually.


-- 
Med Venlig Hilsen

Troels Kofoed Jacobsen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org