[opensource] PDF Editing

Marc Uhrich uhrich.1 at gradsch.ohio-state.edu
Thu Jan 25 15:19:56 EST 2007

Thanks for filling in part of the chasm of omissions in my email.  Not
explaining how to get the compiler and build tools would almost
definitely be a point of confusion for someone with a default install.
And, I learned something new in the gaim trick.

I agree with you and Jim that using KWord to convert the document is
probably a better way for Brian to accomplish his task. In my
experience, modifying PDF documents directly is tricky business.  It's
almost always a better idea to get the original document or convert it
to another format that offers more control.
Marc Uhrich
Systems Engineer @ OSU Graduate School
247 University Hall, 230 N Oval Mall
Columbus, Ohio  43210
(614) 292-6998

-----Original Message-----
From: opensource-bounces at cse.ohio-state.edu
[mailto:opensource-bounces at cse.ohio-state.edu] On Behalf Of Paul Betts
Sent: Thursday, January 25, 2007 1:01 PM
To: Open Source mailing list
Subject: RE: [opensource] PDF Editing

Some notes of mine:

On Thu, 2007-01-25 at 12:03 -0500, Marc Uhrich wrote:
> 2. Uncompress the package run-> tar -zxvf packagename.tar.gz (for
> tar.gz)
or 'tar -xjvf packagename.tar.bz2' (note the 'j')

> 3. Read the README file distributed with the package. This will most
> likely have specific instructions that should be used if they vary
> my included steps 4,5, and 6.

To get the compiler and build tools, run:
sudo apt-get build-essential checkinstall && sudo apt-get build-dep gaim

(Why Gaim? Well, Gaim is a pretty typical GTK+ application; if you pull
in its build dependencies you'll have a lot of what you need)

> 4. In the new directory run-> ./configure (3,4,and 5 require that you
> have development tools installed)

Actually, a better idea is to run ./configure --prefix=/usr/local ; this
makes all the software you've installed manually in /usr/local. Since
this is a small number of programs, it's easier to keep track of then
digging through /usr.

> 5. In the new directory run-> make
> 6. In the new directory run-> make install

Actually, you want "sudo make install", but an even better idea on
Ubuntu is to run 'sudo checkinstall'. This will create a package based
on the program that you can remove later if you want.

> 7. Make a sandwich using rye bread with a meat and cheese of your
> choosing.

I prefer Swiss. Make sure to butter the bread too.

> 8. Toast and enjoy.
> Note: Steps 7 and 8 are optional but encouraged.

> A caveat is that the package may need libraries or other packages
> installed.  In which case, the configure or make will fail.  The
> necessity of these items will be outlined in the README making reading
> it a necessary evil.

Usually you can type "apt-cache search <package-name>" and get some
info, make sure to install the -dev package (like libnm-glib-dev for
example), you need this to compile stuff.

Paul Betts <bettsp at cse.ohio-state.edu>

Opensource mailing list
Opensource at cse.ohio-state.edu

More information about the Opensource mailing list