On Tue, 23 May 2006 00:53:52 -0400, Ignacio José Larrain Aninat
<[EMAIL PROTECTED]> wrote:
You are right, I've seen this implementation elsewhere, I've only
modified it,
probably useless work, but....
Yes, I think it's the update-cvs.sh script in utils/
What if I want to make my own plugins/skins, add others from other
sources,
edit the ones on the repository?
your plugins can reside in the same directory, the update will just mark
them as unknown files, but it won't matter, it won't try to update them or
anything as long as it doesn't have a .svn/ directory.
If you modify the plugins/skins, you'll have them merged on an update, if
there is a conflict, then you modified a line that was also modifed on
SVN so you should fix that... but also, having a symlink is the exact same
thing btw.. you know that ? svn follows the symlink and find .svn/ in the
subdir and updates it too.
Besides, I like the plugins/skins to reside on the program folder, so if
I use
them from another profile, they are still there, and not with the
profile.
I said to put them in ~/.amsn/plugins and ~/.amsn/skins not in
~/.amsn/<profile>/plugins and ~/.amsn/<profile>/skins which means they
will be for all profiles, not just one. But, they will be indeed for only
one unix user, since the home dir changes.. if you want to put them in the
'program files', you can also do it, and mix both dir contents (example,
skins/ will have directoris from amsn-extras but also 'default/' from amsn
module), svn (as well as cvs) should be able to deal with it, maybe not
exactly because there will be a conflict between the two rootdirs, so if a
new plugin is created in amsn-extras, it might not add it because the
.svn/ dir in plugins/ is from the amsn module not the amsn-extras. But for
subdirs, updating the plugins, it should be ok.
Just personal preferences.
I know, we cna't discuss tastes because it's meaningless. You do what you
want, I do what I want, I just wanted to share what I thought because you
might not have thought about doing it that way.
Ignacio
El Martes 16 de Mayo de 2006 12:04, Youness Alaoui escribió:
I don't understand the linking part..
what I have is ont amsn-extras somewhere on my disk, then I did ONCE :
cd ~/.amsn && rm -rf plugins skins && ln -s /path/to/amsn-extras/skins
skins && ln -s /path/to/amsn-extras/plugins plugins
and it's done.. I update amsn-extras and all skins and plugins are
updated... I hate when you get a lot of useless symlinks... one is
enough
KKRT
On Sun, 14 May 2006 22:38:09 -0400, Ignacio José Larrain Aninat
<[EMAIL PROTECTED]> wrote:
> Sorry, I was reading the lists messages and later I've found out.
> I've already updated my script, I'll attach it, maybe it is usefull to
> someone
> else.
>
> greets
> Ignacio
>
> PD: I think I've taken some parts of other scripts (no propietary
ones).
>
> El Domingo 14 de Mayo de 2006 17:36, Harry Vennik escribió:
>> Indeed not much use voting on that. We moved to SVN already!
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
--
KaKaRoTo
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
