WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Request Normalize-Audio  (Read 7236 times)

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9521
Re: Request Normalize-Audio
« Reply #15 on: February 11, 2013, 07:43:29 AM »
True, and I think I will just to keep everyone happy.  But what is being put into question here is the larger issue of our naming convention.

aus9

  • Guest
Re: Request Normalize-Audio
« Reply #16 on: February 11, 2013, 03:08:46 PM »
Hope you don't mind a request for clarification, all can answer
Quote
I by far prefer to use the upstream package and binary name, preferably using lower case letters.   I definitely think we should at least be free to use the upstream name.

But in the past I have received instructions to keep the existing name convention, when the source is named something else
I will name this one as it shows an example of mixed upper and lowercase

libportaudio.tcz........an existing name

upstream url http://www.portaudio.com/

and from license link
Quote
PortAudio Portable Real-Time Audio Library

No I am not trying to rename this tcz just providing an example to see, as I use eyes (sometimes) better than abstraction examples

Question
######

Any reason why we can't used mixed upper and lower case in new tcz submissions?
If there are good reasons ----either way-----I would like to add it to the extensions wiki

IMHO, any new submission "ideally" should respect the upstream naming convention. But that could lead to mixed case?

cheers

Gordon
« Last Edit: February 11, 2013, 03:10:50 PM by aus9 »

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9521
Re: Request Normalize-Audio
« Reply #17 on: February 11, 2013, 05:18:06 PM »
There are several if not many extensions with mixed upper and lower case.  Xvesa, Xorg, perl-Cairo.tcz, etc.   Some names like LaTeX, MPlayer, and others are capitalized in a manner that is hard to remember when the lower case of them is easy.  My personal preference is to use lower case, which is common in the repo.  But there has been and I think should be the freedom to use either lower case or upstream casing.   

Online Rich

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 5892
Re: Request Normalize-Audio
« Reply #18 on: February 11, 2013, 05:30:27 PM »
The one thing that should be avoided is using case to distinguish between extension names. For example:
MPlayer  and mplayer. This will cause problems for people who have their tce directory on a FAT file system
since they cannot co-exist.
 

aus9

  • Guest
Re: Request Normalize-Audio
« Reply #19 on: February 11, 2013, 10:02:40 PM »
Rich

that is great to know

Anyone
Any more juicy bits to share?

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Request Normalize-Audio
« Reply #20 on: February 12, 2013, 08:08:18 AM »
For the record, see here how debian came to change the name:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=250390

And here a related bug report which I think says a lot:
http://savannah.nongnu.org/bugs/?37194
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9521
Re: Request Normalize-Audio
« Reply #21 on: February 12, 2013, 03:37:36 PM »
Added normalize-audio -> normalize symlink for compatibility with scripts made on Debian and non-Debian systems.

Offline SamK

  • Hero Member
  • *****
  • Posts: 713
Re: Request Normalize-Audio
« Reply #22 on: February 12, 2013, 11:22:35 PM »
Added normalize-audio -> normalize symlink for compatibility with scripts made on Debian and non-Debian systems.
Works as expected with scripts created for other formats.  Thanks.

The choice to gain the extra reliability of SCM apps has been improved again.