Problem with tce-updating wpa-supplicant?

[jur]

Code: [Select]

Error on fetch of /mnt/sda7/tce/wpa-supplicant.tcz.md5.txt
Could be a network issue or ...
that this extension has a new name or is no longer supported!


[bmarkus]

Renamed to wpa_supplicant

[Jason W]

Renaming extensions should occur only when absolutely necessary, as it breaks appsaudit and the integrity of existing tce installations.  If the original package is appname-lib, it should be changed to appname_lib upon the next upgrade of the extension.  I personally prefer dashes rather than underscores, but the important thing is to stick with whichever the extension was originally named with.

[Guy]

You have made a number of other things standard.

Why not make this standard too?

Decide whether all extensions should use dashes or underscores, and whatever is decided, all new extensions can then be named that way. At some appropriate time, existing extensions can be renamed to comply.

[Juanito]

My apologies if I inconvenienced users with the name change, but after having completely missed the presence of the berkeley db due to the extension name not matching the source package name, I thought it better to rename the wpa_supplicant extension to match the source package name when it was updated.

[jpeters]

Personally, I don't see much gain in eliminating underscores, since they are used slightly differently (in place of spaces) then hyphens.  Standardizing deps/dep, eliminating tcz?, tce extensions are a different
issue IMHO.

[Jason W]

I guess it is kind of a catch-22, between preserving the upstream source name and standardizing on either dash or underscore.  I have harped on preserving upstream source names, which in general I think is a good idea.  But maybe we can perserve the upstream names except for using dash instead of underscore for the ease of standardization.

My preference would be to deviate from source names to use dash instead of underscore, which would make it easier for remembering extension names. If the dep file had these extensions in it a dash makes creating the dep file simpler and less prone to typos:

Code: [Select]

wpa-supplicant.tcz
gcc-lib.tcz
smallbasic-cli.tcz
docbook-xsl.tcz
gtk2-locale.tcz
gs-common-8.70.tcz

As opposed to:

Code: [Select]

wpa_supplicant.tcz
gcc_lib.tcz
bash-locale.tcz
gtk2_locale.tcz
docbook_xsl.tcz
gc_common-8.70.tcz
gtk-engines.tcz
gtk2_prefs.tcz

I made up some names in the latter to make a point, but using dash in all cases would further simplify the naming structure.

The naming structure has been a work in progress since the beginning,  and we have been living and learning along the way.  When the repo consisted of about 100 extensions, and there was no updating functions, or boot time dep processing, we didn't need to be very particular over the deatails that make a difference now.  But the dash vs underscore has to be one of the last details left to work out.  

When we move extensions to the 3.0 repo, the exsiting ones can be brought into compliance.

[Guy]

Another thing to think about with standardization is program names. If you look at the application names in the menu, some start with small letters, some start with a capital letter, some are all capitals. It would be nice if there was some uniformity.

[Jason W]

Thats a good point. 

Lower cases, dash to seperate, and otherwise preserving upstream package naming would make things pretty uniform.  It may sound like being overly particular, but it would only make life easier.

[Guy]

Is it possible to have spaces in names with more than one word in the menu?

[Jason W]

Spaces in the menu items seem to work ok in the WM's I am familiar with.

[roberts]

I would strongly discourage using spaces in any file or directory name on a nix system. The default window manger uses directory and file names for it menu.

[roberts]

Using dash '-' versus underscore '_' gives much different results when using grep -w. Apparently dash is treated as whitespace while underscore is not.

[Jason W]

Oops, forgot about the directory based menu with flwm.  So even if some WM's accommodate spaces in menu names, menu entries should work with every WM, especially the default one.

And I was unaware of the dash vs underscore issue with grep.  If grep works better with underscore, we could standardize on underscore.

[jpeters]

Oops, forgot about the directory based menu with flwm.  So even if some WM's accommodate spaces in menu names, menu entries should work with every WM, especially the default one.

And I was unaware of the dash vs underscore issue with grep.  If grep works better with underscore, we could standardize on underscore.

Underscores are different than hyphens, so get treated differently. Scripts need to check for naming discrepancies anyway. I'm not against simplification, but would be cautious about overdoing it.