Re: Creating an RPM package from sources with paths that vary

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dunno about the rest of you, but I like to get .src.rpm with all the files in there, in the default SOURCES directory, so I can rebuild packages myself, esp. "foreign" ones. For me it is a maintainability and security issue. I like to think that I could (in principle) fix an annoying bug in a package. Also, I would like (in principle) to be able to view source to make sure there are no "trojans" sneaking in. In practice, that becomes impractical because of the huge volume of stuff/changes.

I find the .nosrc.rpm packages really annoying. Likewise, developer personal filepaths (that don't exist on my systems).

My experience has been that even major distros (Mandrake, SuSE) while they should (again, in principle) be totally recompileable from available .src.rpm, that (in practice!) that is actually not possible. There are some "tweaks" and (time?) dependencies that have crept into the distro process, and some packages get "stuck" (missing source, missing dependency).

Maybe you folks have different experiences?

My preference is:
- no user interaction in .spec or build, i.e. (background) "batch" process
- full sources provided in .src.rpm (unpacked into SOURCES directory, not scattered)

-----Original message-----
From: Matthew Miller mattdm@xxxxxxxxxx
Date: Thu, 11 May 2006 11:11:21 -0230
To: RPM Package Manager rpm-list@xxxxxxxxxx
Subject: Re: Creating an RPM package from sources with paths that vary

> On Thu, May 11, 2006 at 09:49:14AM -0400, Todd Tomaino wrote:
> > example: release/01_00_03/wizbang
> >          release/01_00_04/wizbang
> > I am trying to decide if its best to write a script to gather the files
> > into a single directory, with a known path, and use a spec file that is
> > hard coded to that path to create the RPM. -- OR -- Possibly make the
> > spec file smarter or somehow make it so that the path can be passed into
> > the SPEC.  This would avoid the step of copying the files, and give me
> > one less script to maintain.  I was wondering if anyone has been down
> > this road before and can offer suggestions?
> 
> Why not just use the version in the spec file to automatically generate the
> correct path?
> 
> -- 
> Matthew Miller           mattdm@xxxxxxxxxx          <http://mattdm.org/>
> Boston University Linux      ------>              <http://linux.bu.edu/>
> 
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/rpm-list


Juhan Leemet
Logicognosis, Inc.

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux