Maciej,
Please find some answers below.
On 24/01/2014 12:54, Maciej Wereski wrote:
> First, every repository that uses some Tizen specific paths will have to
> pull libtizenplatform-config-devel in requirements. Currently custom Tizen
Yes.
> macros can be found in packaging/rpm-tizen_macros. Maybe this would be
> better location for these macros?
IMO, no.
By 'packaging/rpm-tizen_macros', you probably mean
platform/upstream/rpm/packaging/rpm-tizen_macros ? This is probably not
a good location, for a few reasons:
- the whole distro build depends on rpm: modifying rpm implies
rebuilding every package. Not sure that OBS admins would agree :-)
- the macros (the names and values) are deduced from the file
tizen-platform.meta when building tizen-platform-config. It's safer to
keep things in the same package and have the rpm macros always synced
with the libtzplatform-config definitions (enum in C header). No build
headaches.
- after all, it's usual for a package to distribute its macros in the
-devel package. Examples: glib2, pango, gtk, ...
> Also current directory macros use other convention: "_${NAME}dir" all
> lowercase, e.g. %{_unittdir}, %{_mandir}. Could these macros be renamed to
> fit this convention?
We chose to keep the same name everywhere:
- C/C++ enums
- bash variables
- env variables
- rpm macros
to avoid any confusion.
Another advantage: when we'll have bugs to fix regarding some paths or
platform vars, it will be easy to grep TZ_XXXX in the source tree.
Actually, grepping '/opt','app' or '5000' is really a hassle.
I hope this clarified things.
Kind regards,
Stéphane
--
Stéphane Desneux
Intel OTC - Vannes/FR
gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
