[Bug 477055] Please drop fonts spec template from rpmdevtools

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=477055





--- Comment #9 from Nicolas Mailhot <nicolas.mailhot at laposte.net>  2008-12-29 05:18:02 EDT ---
(In reply to comment #4)

> > The rpm devs have announced they'll be internalising buildroot creation so
> > anything that tries to manipulate it from scripts is doomed mid-term anyway.
> > And %{buildroot} is both valid and more consistent with the rest of the
> > template
> 
> This has nothing to do with what sets the value of buildroot or how, and
> nothing to do with modifying it.  This is purely a stylistic issue which people
> have very strong opinions on: some people prefer to write specfiles using shell
> style variables, others rpm macro style.  For example whether one wants to
> write "rm -rf $RPM_BUILD_ROOT" or "rm -rf %{buildroot}" in specfiles.  We have
> support for honoring the user's preference in place in newspec if the templates
> are written using the shell style variable syntax - by writing them in macro
> style that preference is taken away (or additional code would need be added
> that does it the other way around, but I'm not sure if it can be robustly
> done).  Again, see Suggestion for point 3 in comment 1 for more details how
> this works currently.

Is it possible for rpmdevtools to support replacing of the macro syntax too?
Because I know many packagers use the templates as plain text templates too
without use of rpmdevtools automation, and I'd really like the default not to
be the shell variant in that case

I also have some opinions on this point :p

Of course it it's absolutely necessary for rpmdevtools I will change this. I
didn't know you were performing post-processing on those parts.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.