Re: [Cdrtools-support] cdda2wav only finds errors

[Joerg S. <Joe...@fo...>]

grarpamp <gra...@gm...> wrote:

> On Wed, Oct 21, 2015 at 6:35 AM, Joerg Schilling
> <Joe...@fo...> wrote:
> >> https://www.google.com/search?q=sccs+to+git
> >
> > Did you find a working script this way?
> > I just see talks without code and links that point nowhere.
>
> Maybe sccs is old enough that, having moved on long ago
> (if they were going to move at all), folks aren't writing / maintaining
> scripts for that anymore, lost to history. Wouldn't be too hard to
> interate each commit, message and timestamp into the filesystem
> and then load that into any other repo, the original timestamps might
> become comments, or bump the clock. Perhaps try going to one
> of the historical intermediates in the same lineage first...
>
> https://www.google.com/search?q=sccs+to+cssc
> https://www.google.com/search?q=sccs+to+rcs
> https://www.google.com/search?q=sccs+to+cvs
> https://www.google.com/search?q=sccs+to+svn

Well, there are of course ways to do this. I just thought that someone might 
have written a script. I did e.g. write a script to convert RCS to SCCS.

BTW: Your search strings helped me to discover that my RCS vs. SCCS text now 
made it to the top of the Google search results:

http://sccs.sourceforge.net/sccs_vs_rcs.html

So it now seems to be easier not to find the unproven claim that RCS is 
supposed to be faster than SCCS.

Regarding CSSC: this could have been a solution in the 1990s but this project 
did never reached a state that makes it a real SCCS replacement. It 
artificially limits the number of deltas to 30000 and is aprox. 30x slower than 
SCCS. 

> Those that know unix know that ;)
>
> > Check e.g. "NSE", "TeamWare" and "KitKeeper".
>
> Which, fortunate or not, are all forgotten by the open
> source community likely due to licenses and lack of
> maintenance and public userbase.

NEW was the base for TeamWare and Teamware was in use by Sun, HP, IBM, AT&T, 
Xerox,.... for development of CDE.

BitKeeper has been developed by one of the co-developers of TeamWare after he 
left Sun.

Thanks to Glenn Skinner, one of the TeamWare project leaders, I know that the 
idea "smoosh" was patented but the patent did time out a year ago. So It now 
just seems the right time to start with SCCS again.

I am sorry that this took too much time, but I did make a negitioation with SCO 
to make SCCS OpenSource in 2001, but then the Linux Company "Caldera Linux" 
bought SCO and there was no interest in OpenSource anymore 2 weeks before the 
source code should have been handed out.

So it took me until December 2006 and negotiations with Sun to make SCCS 
OpenSource.

> > The advantage of SCCS is the history file format that allows a lot of features
> > and that gives the best performance.
> >
> > http://schillix.sourceforge.net/man/man4/sccschangeset.4.html
> > http://schillix.sourceforge.net/man/man4/sccsfile.4.html
>
> There are a lot of good in many things to continue to advocate
> and integrate and deploy, and a lot of market share and good
> stuff in things that users are using today.

If you are interested in dsicussing aspects of a better version control system, 
you are highly welcome!

> > If you know a way to retrieve this, please send the archive.
>
> AFAIK, only the admin of a SF project list can do that somehow,
> see example below. And all the old list homes are dead, so
> you would have the archives to be able to publish them as well.
>
> http://sourceforge.net/projects/msmtp/files/msmtp/msmtp-users/

OK, I thought you have the older archives in mind, e.g. Debian or BerliOS.

Vor SF, there is an interface for the archives at e.g.

https://sourceforge.net/p/cdrtools/mailman/cdrtools-support/

see: https://lists.sourceforge.net/lists/listinfo/cdrtools-support


> > are you satisfied with the recent changes?
>
> cdrtools never let me down yet, and star helped a lot on some
> projects :)

OK, I am still in hope to get feedback from Volker as well.

Jörg

-- 
 EMail:jo...@sc...                    (home) Jörg Schilling D-13353 Berlin
       joe...@fo... (work) Blog: http://schily.blogspot.com/
 URL:  http://cdrecord.org/private/ http://sourceforge.net/projects/schilytools/files/'