This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Generic build script instructions


> So, to answer that question, why not something like this:
> 
>   # --- BEGIN_DEFS ---
>   if [ -f ${FULLPKG}.defs ]; then
>     . ${FULLPKG}.defs
>   fi
>   # --- END_DEFS ---
> 
> So, if my source package name is foo.tar.Z, then I can put the
[snip]
> following in my defs file:
> 
>   # Maintainer defs file for package foo
>   src_orig_pkg_name=foo.tar.Z
>   opt_decomp=z
> 
> This would allow a package maintainer to put specializatons/
> definitions within a defs file for each package, making for
> easier maintentance (except in cases of siginificantly unusual
> packages).
>

That's the first thing that came to my mind when I switched over to using
gbs for packaging mutt.  I'd put an else clause in though and croak if
there's no defs file.

-- 
Gary R. Van Sickle


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]