scott at kitterman
Mar 3, 2007, 6:59 AM
Post #6 of 6
On Saturday 03 March 2007 00:56, Boyd Lynn Gerber wrote:
Re: python-policyd-spf-suse.tar.gz That I used
[In reply to]
> On Fri, 2 Mar 2007, Scott Kitterman wrote:
> > On Friday 02 March 2007 00:41, Boyd Lynn Gerber wrote:
> > > Hello,
> > >
> > > Attached is the file I used for SUSE and the python-policyd-spf
> > I just got a chance to take a look at the spec file for this. That
> > locations that your spec file will install the file is different than
> > that called out in the upstream provided documenation. I recommend that
> > you look at the INSTALL.Debian file and provide a opensuse equivalent
> > that provides the correct path to the executable for your distribution.
> > I'd also change the detailed description to refer to your opensuse
> > specific documentation rather than the Debian specific documentation
> > Also, I didn't see in the spec file where the man page gets installed,
> > not sure if something specific is needed for that or not.
> Here is a beginning. Why do you exclude the files needed from the trunk
> to the distribution? I really think the files should be included. They
> were in .2 but not in .3
From what little I know about spec files, I don't find any problems.
Tumgreyspf, which is the project I derived this from, has a complete spec file
in their source. I took a stab at updating it for this derivative, but don't
know enough to know if what I did was complete or correct. My intent is to
only provide files for the tagged releases that are complete/correct/needed.
I've added your spec file (not updated yet, but I will) to the SVN trunk and
will keep it up to date with whatever changes you provide. That way when I
release the next version, the spec file will be there and this will be
I'm all for putting the packaging information into the tagged releases when I
know it to be correct. I answer to your why question, I think for 0.2 I
copied all the files to the tag and then only included what I saw as the
useful files in the tarball. For 0.3 I think I decided there was little
point in that and I should limit the tagged branch to what I knew to be
correct and needed. The next release will have your spec file and (let me
know which they are) any other of the files that you needed.
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007