Help to make software package

2003-07-09 Thread aparna
Hello,
I m junior programmer in perl. I have creted one patch for Evolution 
mail client .Which will work as filter for
the evolution.It will check all the  incomming mails fron POP3 server 
against one command line scanner. And gives the appropriate output in 
the mail.
So i want to make one tar file which will contain my perl script , the 
commandline scanner rpm and one more binary.
So how to make make file for this kind of operation. i have never 
created such package. So please kindly help me .

Thank you
Aparna Sawant



Re: Help to make software package

2003-07-09 Thread Ed Avis
On Wed, 9 Jul 2003, aparna wrote:

So i want to make one tar file which will contain my perl script ,
the commandline scanner rpm and one more binary.

Why would you want the perl script and the RPM in the same tar file?  
That's not normally the way things are done.

Start by writing a Makefile.PL for your script (assuming you want to
use MakeMaker) so that it can be installed with 'perl
Makefile.PL; make install'.  Then once this is working you can package
it as an RPM using a tool like makerpm.pl, cpan2rpm or RPM::Specfile.

Then you can distribute the RPM package together with any other RPM
packages you want to accompany it.  But mixing together Perl source,
RPM packages and binaries is not usually a good idea.

-- 
Ed Avis [EMAIL PROTECTED]





ANNOUNCE: Module::Build 0.19 released

2003-07-09 Thread Ken Williams
Hi,

The uploaded file

Module-Build-0.19.tar.gz

has entered CPAN as

  file: $CPAN/authors/id/K/KW/KWILLIAMS/Module-Build-0.19.tar.gz
  size: 74015 bytes
   md5: c1647888d63033446583f9697fb7b426
Oodles and oodles of changes since 0.18:

 - Added support for the 'install_path' parameter, which allows custom
   specification of where things should be installed.  This is a major
   improvement to Module::Build's functionality.
 - Added the 'install_base' parameter.  Provides an easy way to
   install to local or alternative directory trees.
 - We now install scripts by default to $Config{installsitebin}
   instead of $Config{installscript}.  Neither is a great choice, but
   the former is likely to be [analogous to] /usr/local/bin, and the
   latter is likely to be [something like] /usr/bin .  If/when there's
   a $Config{installsitescript}, we'll start using that automatically.
 - Fixed a problem on Win32 in which C and XS files wouldn't be
   compiled properly, and the user would see an error about 'Can't
   locate object method format_compiler_cmd'.
   (http://rt.cpan.org/Ticket/Display.html?id=2391)
 - We now use the correct perl interpreter (via
   Module::Build-find_perl_interpreter) in pass-through makefiles.
 - The t/compat.t test now uses $Config{make} instead of just 'make'
   to test makefile compatibility.  This fixes some failures on Win32.
   We also skip this test entirely if no make utility is available.
 - Alternative distribution layouts are now supported via the
   'pm_files', 'pod_files', 'xs_files', 'PL_files', and 'script_files'
   parameters to new().  This should help people transition from
   MakeMaker, and might even help us write an automatic transition
   tool.
 - Added tests to t/runthrough.t that check to see installation is
   happening correctly.
 - Added experimental code to build a .ppd file, in support of
   ActiveState's Perl Package Manager. [original patch by Dave
   Rolsky]
 - For authors who use Module::Signature to sign their distributions,
   we now create the SIGNATURE file right in the distribution
   directory, rather than creating it in the top-level directory and
   copying it into place.  This solves problems related to having
   files get out of date with respect to their signatures.
 - We now don't depend on Module::Info to scan for packages during the
   'dist' action anymore, because it's way too aggressive about
   loading other modules that you may not want loaded.  We now just
   (ick, yuck) scan the .pm files with a regular expression to find
   package Foo::Bar; statements.
 - Silenced some annoying copyright/logo output from Microsoft 'nmake'
   during Makefile compatibility testing. [Randy W. Sims]
 - Command-line arguments may now either be specified using the syntax
   '--foo foovalue' as well as the traditional syntax 'foo=foovalue'.
   The former is often more convenient for shell tab-completion when
   the value is a filename (as in 'Build test --test_files t/basic.t').
 - Command-line arguments may now include non-named parameters, which
   make some actions more natural.  For instance, the 'diff' action
   may now be invoked as 'Build diff -u' rather than as
   'Build diff flags=-u'.
 - Pass-through Makefile.PLs now convert unknown Makefile.PL
   parameters to lower-case and hand them to Build.PL, rather than
   ignoring them.  This means we only have to account for the
   differences in the interface, not the entire interface, in
   translating parameters.
 - We now issue a warning  don't proceed if asked to make a distdir
   and there's no MANIFEST or it's empty.
 - Moved INSTALL to INSTALL.txt to increase compatibility with various
   odd versions of 'make' during 'make install' on case-insensitive
   filesystems (like nmake on Win32, often).  Only affects the
   Makefile compatibility layer.  [reported by Andrew Savige]
 - Module::Build-known_actions() now works as a class method.

 - Pass-through makefiles now list each action individually rather
   than using a .DEFAULT catch-all.  This improves compatibility
   with 'nmake' on Win32, and probably some other less common 'make'
   dialects.  [Andrew Savige]
 - We're now more aggressive about testing the pass-through makefiles,
   e.g. making sure they can run 'all' and 'test' targets, and making
   sure the Makefile itself actually exists.
 - Fixed a problem with check_installed_status() when installed
   version contains non-numeric characters like underscores.
 - Fixed a problem with a bareword 'File::Spec' in one of the test
   scripts that caused it not to compile under 5.8.0 (but is fine
   under 5.6).
 - Fixed a problem with the 'destdir' installation parameter on
   platforms that have volume identifiers in path names (like C: on
   Win32).  The identifier is now stripped from installation
   directories before prepending the destdir path.  The destdir path
   may still have a volume identifier on it.
 - Added an 'add_to_cleanup' parameter to new() that calls