Re: prominent message on website about "use only on

Am Mon, 31 Jul 2017 17:25:03 -0300
schrieb Rogério Brito <[email protected]>: 

> I'm sorry if this has already been mentioned here, but this seems like
> an excellent opportunity to switch to git.

An easier migration would be to subversion, though. It supports proper
branching and merging nowadays and the migration from CVS is very well
established, along with easy migration of the mind as the command set
is very similar. There is an easy-to-grasp (IMHO) methaphor of a file
system tree where branches and tags are just copies with some projected
semantics. Version History is linear with simple revision numbers and
not easily meddled with, like CVS.

Also you can version other stuff outside the actual code in
trunk or branches. For mpg123, I simply version the website along
mpg123 itself in the same subversion repository. You don't want to see
that when checking out the code for hacking or in a release tarball.

I know everyone is moving to git, even github, and the kids give you an
unbelieving stare when you mention revision control as a general
concept and not just another name for git. Git is very powerful and it
very well suits large active projects with many developers working
together, but not every use-case needs that. Other revision control
systems have advantages over git, too. Maybe even the simple stuff like
being able to version empty directories, or checking out only parts of
a tree. Or have a revision number that you can understand as a point in
time.

I guess lame will move to git like everybody else. I just wanted to
voice that there indeed are alternatives (of course also the other
distributed ones). I don't like monopolies and for some reason, despite
somewhat working with it for about 10 years now (other projects than
mpg123), I still don't really like git. I admit that I also would
welcome a move from CVS as I only briefly used it before jumping to
Subversion. But given the low expected rate of change of the very
mature project, there is no pressing need at all to change development
tools when the main issue is lack of anyone doing work to begin with.

If the only one to actually contribute is doing the migration to be
able to bear working on lame, then I see the point, though;-) After
all, the tools are secondary. Code counts.

I am still trying to get my head into the mpglib usage in lame. One
possible showstopper is that you want samples as unclipped double numbers on
occasion. I hope I can change that to single-precision float. You get
that from a standard build of libmpg123, while double would mean that
we need to configure a copy of libmpg123 in-tree. Any real use case for
double-precision PCM samples?


Alrighty then,

Thomas


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev