TheProjecter / ultimate-gnome

Automatically exported from code.google.com/p/ultimate-gnome
0 stars 0 forks source link

Create a new releaser #21

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What you need to do is:
Create a new releaser script that uses the same structure of the cleaner
and that with one option could use the cleaner itself.
Maybe I need to create some structure (directory) for exporting png.

What you have to do when finished:
verify all

Original issue reported on code.google.com by newmooon on 30 Nov 2008 at 8:18

GoogleCodeExporter commented 8 years ago
I need a script that could insert also the release name if I specify it 
otherwise it
will set the "test" version .

Original comment by newmooon on 30 Nov 2008 at 8:46

GoogleCodeExporter commented 8 years ago
I need to edit the Cleaner script and use it to decide where the working copy 
is.
Then I'll call the release process from lib and use it to create a package.

Original comment by newmooon on 21 Jan 2009 at 9:26

GoogleCodeExporter commented 8 years ago
a small package builder has been added at r464 now I've decided not to add a
parameter to write automatically the version number it is useless.

Original comment by newmooon on 21 Jan 2009 at 12:45

GoogleCodeExporter commented 8 years ago
I'm working now on a version of the package builder that could export svg files 
and
at the same time mantains symlinks.

Original comment by newmooon on 21 Jan 2009 at 2:10

GoogleCodeExporter commented 8 years ago
I'm changing the script now in a way it could decide if a symlink should be 
created
with "ln -s name1 name2" or "ln -s dest1" with a code like this

string="../file.svg"
line=`expr match "$string" '\(../\)'`;
echo $line

if [ "$line" = "" ]; then
    echo "not match";
fi
echo "fine"

I test if the symlink points out of the directory or in the directory 

Original comment by newmooon on 22 Jan 2009 at 9:36

GoogleCodeExporter commented 8 years ago
Now it's almost finished I've found that some files are not wrongly changed 
from .svg
to ..png this cause them not to be deleted so you could find under 

8x8/emblems:

emblem-noread..png
emblem-nowrite..png
stock_mail-priority-high..png

8x8/mimetypes

gnome-fs-regular..png
gtk-file..png
text-plain..png

8x8/places

gnome-fs-directory..png
gnome-fs-ftp..png
gnome-fs-nfs..png
gnome-fs-share..png
gnome-fs-smb..png
gnome-fs-ssh..png
gnome-mime-x-directory-smb-share..png
gtk-directory..png
network..png
stock_folder..png

8x8/status

folder_open..png
gnome-fs-directory-accept..png
gnome-fs-directory-visiting..png
gtk-directory..png
stock_open..png

Original comment by newmooon on 22 Jan 2009 at 10:46

GoogleCodeExporter commented 8 years ago
it is the same on every resolution. I should find why this files are wrong 
manipulated.

Original comment by newmooon on 22 Jan 2009 at 10:48

GoogleCodeExporter commented 8 years ago
I found the problem. It is because the "find" command is defined as "find ./ 
-type l"
and also a file of the type file.icon if a symlink is included in the list, 
adding
"-name *.svg" fix the problem, bur on this computer (university) it gives an 
error :
"path must precede expressions"but I think it does so. I don't understand, I-ll 
check
it at home. 

Original comment by newmooon on 22 Jan 2009 at 3:49

GoogleCodeExporter commented 8 years ago
Yes the problem seem s to be in the find command, this is what I've found on 
the web.
E.g.. if you had the following directories in the local path
Code:

pg2xbase-2.3.2
pgaccess-0.98.8
pgadmin3-1.2.2
pgmanage-src
pgsql_session_handler.php
php
phpPgAdmin
php_sessions.sql
platform
pme-1.0.4

and you searched for
Code:

find . -name php*

you'd be getting the following (somewhat bewildering) error-message:
Code:

$ find -name php*
find: paths must precede expression
Usage: find [path...] [expression]

which won't happen if you do it like this:
Code:

$ find -name "php*"

So I'll correct it now.

Original comment by newmooon on 22 Jan 2009 at 6:14

GoogleCodeExporter commented 8 years ago
I've fixed it and now at revision r476 (fixed and verified)

Original comment by newmooon on 22 Jan 2009 at 6:37