[indiana-discuss] src packages

[Jonathan Edwards]

On Dec 10, 2008, at 11:17 AM, Nicolas Williams wrote:

> On Wed, Dec 10, 2008 at 10:02:56AM +0000, Robert Milkowski wrote:
>> NW> JDS and the projects to populate /pending and /contrib -- all  
>> could (and
>> NW> should and will) deliver pointers to spec files for rebuilding  
>> their
>> NW> pkgs.  SFW, ON, not so much, but then who want to build from  
>> source can
>> NW> always pull and run nightly.
>>
>> But that's my point - it's way more difficult to do it on OS than on
>> Linux with src rpm's - I need to find some spec files, manually
>> download software, find out dependencies then cross fingers and try  
>> to
>> compile, then most of the time manually build a package... and all of
>> that to recompile apache with one extra option. On Linux one just
>> downloads src rpm, quick vi then one command and one gets a binary
>> package.
>
> I feel like I'm repeating myself: the task can be automated, and Jim
> even claims it has been (I've not used that tool, so I can't confirm).

but it's not part of the spec file that tracks standard configure  
options for any given build .. and i think that's the point .. eg:

$ ls samba/packaging/RHEL
makerpms.sh.tmpl	samba.spec.tmpl		setup

---
here standard RHEL configure, build options, and postinstall steps are  
included in the spec file .. vs
---

$ ls samba/packaging/Solaris/
README			pkginfo.master		request
copyright		postinstall		samba.init.master
i.swat			preremove		services
inetd.conf.master	prototype.master	smb.conf.default
makepkg.sh		r.swat

---
where makepkg.sh (SVR4 style) assumes that you've already built samba,  
and our distributed samba configure options are tucked away in our  
Makefile.sfw along with extra patches in the sfw tree that we've been  
applying and maintaining separately for a while now.

hth
---
.je