Hi,
that will be nice ;) perhabs it would be damage the rss_feed if use a number in the package name? But I may be able to ignore such a thing in my rss_feed.lib ;) If it possible a package named "themes" and as release perhabs no number - or must it be given (I don't really know)? The release number could be stored in the file-name like theme_name-2.6.1-2.6.x.zip.
All themes (I've checked) are working with 2.6.x, garvBlue requires 2.6.1 or higher. There's no "bad code" (like mailing passwords or such a thing) and all themes are checked to be valid css level 2.
I'm making a layout for downloading themes. Should we put some screens for each theme (I think one screen each theme would be enough) like in theme.php in the PMA-Application?
Regards
Michael
Marc Delisle schrieb:
each theme is a 90K file. Because I cannot see how to make sub-directory of packages, if I create separate packages, it will IMO look very weird on this page: https://sourceforge.net/projects/phpmyadmin/
especially if the number of themes grow.
I would prefer a package named "themes" with a release of 2.6.1. Then when we release PMA 2.6.2, we could release in the package "themes" a release of 2.6.1-2.6.2 (minimum-maximum versions).
Marc