RE: [Rpmrebuild-project] Spliitting spec file

[Reznic V. <Val...@co...>]

> -----Original Message-----
> From: Eric Gerbier [mailto:eri...@me...]=20
> Sent: Thursday, October 14, 2004 11:06 AM
> To: rpm...@li...
> Subject: Re: [Rpmrebuild-project] Spliitting spec file
>=20
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Subject:* [Rpmrebuild-project] Spliitting spec file
> >
> > Hi, Eric.
> >
> > Now all (but RPM_BUILD_ROOT) env variables are prefixed=20
> with RPMREBUILD_
> > (checked in)
>=20
> ok
> But you do not fill the Changelog file with your changes
>=20
> > I began to describe in manpage how plugin work, but realize=20
> that problem
> > with plugins is still here.
> >
> > The problem is related to plugins, which need to change specfile.
> >
> > Parse spec file and find relevant part isn't easy task.
>=20
> I know !
>=20
> > Worse, if in the new rpm version will be added new section=20
> (not tag like
> > Summary:, but like %description or "%post")
> >
> > Filter which look for the all possible % names as end of=20
> appropriative
> > part will be broken.
> > What you think about this ?
>=20
> this is a very good idea !

You don't comment this (or may be yours  > this is a very good idea ! Is
related to the part below:

So, may be better, during query create different files:=20
- preambel,
- reqs
- prov
- files
- post,
- pre,
...
Etc

Process them (it should be more easy) and after that concatenate to
resulting spec.

What you think about this ?

By the way, if we going this way it we'll need change --edit
implementation too - or invoke edit for=20
Specific part of the spec, or invoke edit for all of them.

Valery
>=20
> how to release a new version with the current changes ?
I am not finish manpage changes yet.
> (I do not like to have too much changes, I prefer "change=20
> often, release often")
I too. But in this case all the change is about plugins interface and I
don't think
That change interface and after that change it again is a good thing.
So,if we are going to splt generated spec file to make plugins writers
life easier
I'll prefer to finish this change and release version (may be 2.0.0)

Valery


>=20
> - --
> Eric Gerbier
> http://webminstats.sourceforge.net
> http://rpmrebuild.sourceforge.net
> http://afick.sourceforge.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>=20
> iD8DBQFBbkGONzh6q8tvpCoRAts8AJsGS5cE3ZmzP7HJ3u7F1hcX9sae2wCfU57h
> rIbqtIrK/Inlbf26krynES8=3D
> =3DYs9m
> -----END PGP SIGNATURE-----
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on=20
> ITManagersJournal
> Use IT products in your business? Tell us what you think of=20
> them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to=20
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Rpmrebuild-project mailing list
> Rpm...@li...
> https://lists.sourceforge.net/lists/listinfo/rpmrebuild-project
> ______________________________________________________________________
>   This email message has been scanned by PineApp Mail-Secure=20
> and has been found clean.
>=20