Just recently i tried to apply the GNU Autotools to my project, while it was possible, it took forever to know where to create which files and what to place in each of them.
Dare you making a space rather than a tab!
Inspired by GNU Autotools, and overhelmed by its functionality and complexety, i wanted something simpler, smaller, quicker for my smaller projects - that do no require compiling.
While i do respect and honor their work, for a 'simple script project' the Autotools are somewhat overpowered and hard to handle.
While i consider myselft a fast adapter/learner, and thinking about how much trouble i had, i could imagine others having more trouble with the GNU Autotools.
So, YASSI was born.
It creates 3 make-* files, and a 'reference' file - doRef=true will install it to /etc/$APP.conf
make-distclean, would remove the just created files, cleaning up your project dir
Since this tool/google+ post has had more shares and likes in less time than any of my other posts (on G+) i thought i'd share it here for those without G+.
I am writing an installation script on AIX. This involves typical checks of some pre requisites like java, oracle, some version checks, disk space etc. It is a long script. I am facing a strange problem. There are a no of functions used in the script. What I see is that the installer complains of... (1 Reply)
Hey Guys,
Can somebody help me get a unix OS installer (preferably no charge)?
Can I install it on intel pc? I got a copy of unix installer a year ago and tried installing it on an intel pc but I can't get it done although I was already following instructions.
Slick (42 Replies)
My n00b question:
I am trying to write a script that I can place on a flash drive and then move from computer to computer and install a file, which is bundled with the script. (ie the script is at /Volumes/FlashDrive/Folder/Script, the file is at /Volumes/FlashDrive/Folder/File)
So far I have... (1 Reply)
I have a software bundle for which I want to create an installer. One of the things I am also looking at, is to be able to install this straight from a CD or any external storage device. How do I go about creating one? This is for Linux.
Any advice is welcome !!
--
garric (3 Replies)
Hello all!
This is my first post and I'm very new to programming. I would like help creating a simple perl or bash script that I will be using in my work as a junior bioinformatician.
Essentially, I would like to take a tab-delimted or .csv text with 3 columns and write them to a "3D" matrix:
... (16 Replies)
Hi team,
I have two select statements and need to run them using SYSDBA user
select * from temp_temp_seg_usage;
select segment_name, tablespace_name, bytes/ (1024*1024) UsedMb from
dba_segments where segment_name='TEMP_TEMP_SEG_USAGE';
Need to run this using a shell script say named... (1 Reply)
Xfce desktop installer script on Ubuntu for home, office or server computers.
This script installs Xfce desktop and a set of programs according to user needs starting from an Ubuntu Server base system. It's valid for netbooks, notebooks, desktop computers and servers.
For more information... (1 Reply)
Hi, I have a little problem with an Installer.
In my script I have a section that place a keyboard shortcut:
#!/usr/bin/perl
################################################################################
#
# Create Desktop shortcut for Swedish Menu Commands Document
#... (1 Reply)
Hi Guys,
I have one installer shell script which normally get from the dev team to install the app and it works fine for years (in IAX) the same installer/script iam trying to run in Linux 7.2 but it stuck somewhere which I cannot debug, can you help me to point out where it stuck .
here is the... (9 Replies)
Heyas
As someone said he'd like to see some more projects posts on the forum, so, here's one I hope is ready.
Not so much fun-fun, but practical ;)
I hope...
So, you have that small non-arch project you would like to install, but get the feeling that GNU Autoconf is a bit too 'massive' for... (2 Replies)
Discussion started by: sea
2 Replies
LEARN ABOUT CENTOS
po4a-runtime.7
PO4A-RUNTIME.7(7) User Contributed Perl Documentation PO4A-RUNTIME.7(7)NAME
po4a-runtime - po4a and runtime gettext translation without Autotools
Introduction
With po4a-build, po4a also includes support for adding translation of runtime script output messages using gettext but without requiring
the package to adopt Autotools and the typical ./configure process.
Using example Makefile snippets, packages can harness intltool with minimal effort.
Layout
Documentation translation should NOT use the same po/ directory as the runtime translation. Whilst runtime translation can use directories
other than po/, it is usually easiest to go with the convention.
Multiple languages
Just a word on packages that use scripts in multiple programming languages. A common mix is Perl and shell. Note bene: gettext WILL get
confused and omit strings from one or other language unless file extensions are used for whichever is the least problematic language.
When using multiple languages, experiment with various settings in po/Makevars until you get all the strings you need in the POT file.
In particular, specifying two languages in po/Makevars can be problematic. Instead of:
# Don't do this:
XGETTEXT_OPTIONS = -L Perl -L Shell --from-code=iso-8859-1
Consider renaming (or providing symlink(s) for) all files for one of the languages involved and omitting the explicit -L options. The file
extension only needs to exist during the time that po/POTFILES.in is being processed.
The --keywords option can also be useful - see the xgettext documentation.
Populating po/
So, create your top level po/ directory and then use the example files in /usr/share/doc/po4a/examples/ to populate it.
LINGUAS
Must exist, even if empty. Consists of a list of translations - each line not starting with a '#' must match an existing PO file. e.g.
if LINGUAS contains a single line, 'fr', an fr.po file must exist alongside the LINGUAS file.
$ cat po/LINGUAS
cs
de
fr
$
By convention, the LINGUAS file is sorted alphabetically but that is a manual process.
POTFILES.in
The list of files containing the messages that need to be translated at runtime - i.e. your scripts. If you've used the top level po/
directory, the paths should be relative to the top level directory, not the po/ directory itself.
$ ls -l
myscript.pl
another.pl
foo/support.pl
po/
po/POTFILES.in
$ cat po/POTFILES.in
myscript.pl
another.pl
foo/support.pl
$
Note that it is explicitly supported that the scripts themselves can contain strings for both runtime and documentation translation,
e.g. using gettext functions for runtime and embedded POD content for documentation. So it is not a problem to have the same file
listed in po/POTFILES.in and doc/po4a-build.conf
Makevars-perl.example
If your scripts are in Perl, copy this example file as po/Makevars and edit it to suit.
Makevars-shell.example
If your scripts are in shell, copy this example file as po/Makevars and edit it to suit.
po4a-build.make
Copy this example file as po/Makefile - it shouldn't need editing but you may want to keep it updated against
/usr/share/doc/po4a/examples/po4a-build.make as it may need to be updated within po4a releases as the underlying intltool support
changes. (The file itself was generated from another project using Autotools and intltool.)
Building
These snippets need to be added to your top level Makefile or whatever other method you use to prepare your sources for distribution.
clean:
$(MAKE) -C po/ clean
install:
$(MAKE) -C po/ install DESTDIR=$(DESTDIR)
dist:
$(MAKE) -C po/ pot
(In an Autotools project, this would happen automatically by simply adding po to the "SUBDIRS" value in Makefile.am.)
Maintenance
Runtime translation isn't quite as easy as po4a-build in that adding a new translation does require editing po/LINGUAS, but apart from
that, updating translations is merely a case of replacing the relevant PO file with the new version.
Depending on how you prepare your source tarball, you may also need to list new PO files in the MANIFEST file or add to the script(s) that
prepare the tarball. (That also applies to po4a-build.)
Any *.mo or *.gmo files in po/ can be deleted / cleaned up.
Copyright
Whilst the example files are part of the po4a project, you are free to use, modify and distribute them in your own projects without needing
to refer back to po4a or list the po4a team in your own copyright notices, in the same manner as other build tools like Automake itself.
If you want to mention po4a, that is fine too.
AUTHORS
Neil Williams <linux@codehelp.co.uk>
perl v5.14.2 2012-05-17 PO4A-RUNTIME.7(7)