No subject

good solution as it wont work with csh, zsh, with which i agree, but
couldnt think of a better solution until now.

----------
All above here is the actual question
----------
Now the idea came up to place the 'base-script' (st) in /usr/bin, while
everything else would be in a folder somewhere. However, this has a hughe
drawback, as it (the script tools) wont work in this mixed up (split away)
environment.
Until now, one could have been sure, that in any case if i move the
directory the scripts tools are in, anywhere else, one could just execute
the main script and everything kept working.
This was achieved by symlinking the actualy path to /usr/share/%name, of
course only if it wasnt installed there using rpm/yum (default).

Now after all this crapy text (its past midnight here), according to the
feedback (very little) i have recieved so far,
i do need feedback/info, from someone capable handling complex bash script
structures across folders, using other scripts are libraries, offering the
users to write their own libs and scripts.
Further, it takes some use of 'configuration' files, uses some sort of
templates and lots of other stuff.

It is NOT an easy task, to review, or to understand how it works, or to
actualy give any kind of advice.
I do know and understand this, thus i would appreciate any usefull feedback
even more for the very same reason.

For more info about this package, please have a look at
http://sea.hostingsociety.com/?p=Script-Tools&stc= many, but not all,
things are explained there, or at least try to be there.
Have i mentioned, i lack of feedback/questions so i could not write the
readme appropriate to the 'demand' of explanation.

Where would be the proper place to put/package my script tools to?

Thank you in advance for any hints, advices, questions or suggestions.
Kind regards
~sea~

-- 
Simon A. Erat (sea)
Switzerland
----------------
FAS: sea
IRC: seasc

--bcaec54ee3eea6d45404c495b57d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Heyas<div><br></div><div>As i&#39;m new to packaging, specificly to linux, =
i am a little confused at this moment.</div><div>I have my scripts (kind of=
 framework, but for any enduser they are just tools) which i&#39;d like to =
be shiped with Fedora,=A0however, until now i was thinking like:</div>
<div>My Package =3D Additional Software =3D /usr/share/%name.</div><div><br=
></div><div>Now that i had opened a Review Request (<a href=3D"https://bugz=
illa.redhat.com/show_bug.cgi?id=3D835089">https://bugzilla.redhat.com/show_=
bug.cgi?id=3D835089</a>), someone asked my whe i didnt pack my scripts into=
 /usr/bin.</div>
<div>Allthought i like this idea, i do not feel that this would be &#39;cle=
an&#39;, as my script tools base upon a directory structure, while there ar=
e no directories in /usr/bin.<br clear=3D"all"><div><br></div><div>From the=
 same person i was told that /etc/profile.d/%name.sh would not be a good so=
lution as it wont work with csh, zsh, with which i agree, but couldnt think=
 of a better solution until now.</div>
<div><br></div><div>----------</div><div>All above here is the actual quest=
ion</div><div>----------</div><div><div>Now the idea came up to place the &=
#39;base-script&#39; (st) in /usr/bin, while everything else would be in a =
folder somewhere. However, this has a hughe drawback, as it (the script too=
ls) wont work in this mixed up (split away) environment.</div>
<div>Until now, one could have been sure, that in any case if i move the di=
rectory the scripts tools are in, anywhere else, one could just execute the=
 main script and everything kept working.</div></div><div>This was achieved=
 by symlinking the actualy path to /usr/share/%name, of course only if it w=
asnt installed there using rpm/yum (default).</div>
<div><br></div><div>Now after all this crapy text (its past midnight here),=
 according to the feedback (very little) i have recieved so far,</div><div>=
i do need feedback/info, from someone capable handling complex bash script =
structures across folders, using other scripts are libraries, offering the =
users to write their own libs and scripts.</div>
<div>Further, it takes some use of &#39;configuration&#39; files, uses some=
 sort of templates and lots of other stuff.</div><div><br></div><div>It is =
NOT an easy task, to review, or to understand how it works, or to actualy g=
ive any kind of advice.</div>
<div>I do know and understand this, thus i would appreciate any usefull fee=
dback even more for the very same reason.</div><div><br></div><div>For more=
 info about this package, please have a look at=A0<a href=3D"http://sea.hos=
tingsociety.com/?p=3DScript-Tools&amp;stc=3D">http://sea.hostingsociety.com=
/?p=3DScript-Tools&amp;stc=3D</a>=A0many, but not all, things are explained=
 there, or at least try to be there.</div>
<div>Have i mentioned, i lack of feedback/questions so i could not write th=
e readme appropriate to the &#39;demand&#39; of explanation.</div><div><br>=
</div><div>Where would be the proper place to put/package my script tools t=
o?</div>
<div><br></div><div>Thank you in advance for any hints, advices, questions =
or suggestions.</div><div>Kind regards</div><div>~sea~</div><div><br></div>=
-- <br>Simon A. Erat (sea)<br>Switzerland<br>----------------<br>FAS: sea<b=
r>
IRC: seasc<br><br>
</div>

--bcaec54ee3eea6d45404c495b57d--