Re: [Slackbuilds-users] Tracking version releases

On 20/06/17 20:32, David Melik wrote: > On 06/20/2017 02:51 AM, Christoph Willing wrote: >> On 20/06/17 17:57, David Melik wrote: >> https://github.com/cwilling/pvc [...] >>> Error: ENOENT: no such file or directory, scandir >>> '/home/d/.local/share/pvc' >> >> That's a bit embarrassing

Re: [Slackbuilds-users] Tracking version releases

On 06/20/2017 02:51 AM, Christoph Willing wrote: On 20/06/17 17:57, David Melik wrote: https://github.com/cwilling/pvc [...] Error: ENOENT: no such file or directory, scandir '/home/d/.local/share/pvc' That's a bit embarrassing - sorry about that. I'm just about to upload a proper fix

Re: [Slackbuilds-users] Tracking version releases

On 20/06/17 17:57, David Melik wrote: >> https://github.com/cwilling/pvc [...] > > I need that because many projects are notorious for not announcing new > versions; they could not care less that package maintainers spread > projects' software. Many projects are switching from newsgroups, >

Re: [Slackbuilds-users] Tracking version releases

On 05/11/2017 10:15 PM, Christoph Willing wrote: [...] I don't have a huge number of SlackBuilds to maintain but enough that its easy to lose track of upstream development and know when new versions have been released. Occasionally I do a find of .info files containing my name in the SBo file

Re: [Slackbuilds-users] Tracking version releases

On 12/05/17 15:15, Christoph Willing wrote: > Hi all, > > I don't have a huge number of SlackBuilds to maintain but enough that > its easy to lose track of upstream development and know when new > versions have been released. Occasionally I do a find of .info files > containing my name in the SBo

Re: [Slackbuilds-users] Tracking version releases

On 05/11/2017 11:20 PM, Willy Sudiarto Raharjo wrote: >> of thing. There has to be a better way, so does anyone already have a >> better way to keep track before I write something to do it? > > Have you checked repology? >

Re: [Slackbuilds-users] Tracking version releases

On 13/05/17 12:01, Kyle Guinn wrote: > On 5/12/17, Christoph Willing wrote: >> On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: No I hadn't seen that. It looks pretty good - despite a few odd little things e.g. live555 versioning string incorrectly makes it

Re: [Slackbuilds-users] Tracking version releases

On 5/12/17, Christoph Willing wrote: > On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >>> No I hadn't seen that. It looks pretty good - despite a few odd little >>> things e.g. live555 versioning string incorrectly makes it think a >>> version from 2014 is the

Re: [Slackbuilds-users] Tracking version releases

I have my own script to keep track of projects I maintain sbuilds for (or other stuff). It consists of a config file containing name,version,updated flag,browser,url for each project and the main script has a big case statement, where I add one-liner subscripts for each project's web page to

Re: [Slackbuilds-users] Tracking version releases

that seems useful! The way I keep track on my updates is a bit more manual. I have a list of what I maintain in my humble blog: https://slackalaxy.com/slackbuilds/ Every couple of months or so, when I know that I have a (relatively) free weekend ahead of me, I go through the entries, visiting

Re: [Slackbuilds-users] Tracking version releases

On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >> No I hadn't seen that. It looks pretty good - despite a few odd little >> things e.g. live555 versioning string incorrectly makes it think a >> version from 2014 is the latest. >> >> Hmmm what to do? > > There's nothing we can do except that we

Re: [Slackbuilds-users] Tracking version releases

> No I hadn't seen that. It looks pretty good - despite a few odd little > things e.g. live555 versioning string incorrectly makes it think a > version from 2014 is the latest. > > Hmmm what to do? There's nothing we can do except that we had to check for upstream. Different distribution have

Re: [Slackbuilds-users] Tracking version releases

On 12/05/17 16:20, Willy Sudiarto Raharjo wrote: >> of thing. There has to be a better way, so does anyone already have a >> better way to keep track before I write something to do it? > > Have you checked repology? >

Re: [Slackbuilds-users] Tracking version releases

> of thing. There has to be a better way, so does anyone already have a > better way to keep track before I write something to do it? Have you checked repology? https://repology.org/metapackages/outdated-by-maintainer/chris.willing%40linux.com/ it's not up to date due to a typo in one of the

Re: [Slackbuilds-users] Tracking version releases

On 12/05/17 15:23, Jeremy Hansen wrote: > I don't have any immediate thoughts on what else to support, but maybe > you could set up something like plowshare​ does in regards to "modules". > You have the main program that has all the binaries, then you have > modules for all the various sites that

Re: [Slackbuilds-users] Tracking version releases

On Fri, May 12, 2017, 1:16 AM Christoph Willing wrote: > Hi all, > > I don't have a huge number of SlackBuilds to maintain but enough that > its easy to lose track of upstream development and know when new > versions have been released. Occasionally I do a find of

[Slackbuilds-users] Tracking version releases

Hi all, I don't have a huge number of SlackBuilds to maintain but enough that its easy to lose track of upstream development and know when new versions have been released. Occasionally I do a find of .info files containing my name in the SBo file tree and go to each of the relevant websites