The attached specfile creates a dummy package which will create and own
/usr/share/wallpapers/ which is currently owned by kdebase-common (and
possibly by other packages).  However, it is quite plausible that other
packages that would have no reason to require KDE, thus implying that
some type of ownership of that directory would be required.

This aims to solve that problem by abstracting the ownership of the
directory; packages putting stuff in this directory would simply require
this package and ownership is no longer a problem.  This also clears the
way for a standardized location for wallpaper files, regardless of
source.

Obviously similar packagess could be made for directories where multiple
packages that have no need for dependencies or conflicts between them.

WDYT?

-- 
Levi Ramsey
[EMAIL PROTECTED]                           [EMAIL PROTECTED]

Take due notice and govern yourselves accordingly.
Currently playing: Metallica - S&M - No Leaf Clover
Linux 2.4.21-3mdk
 17:29:00 up 8 days,  2:47, 12 users,  load average: 0.21, 0.20, 0.18
%define name wallpaper-dir
%define version 1
%define release 1mdk

Summary:                Dummy package to own wallpapers directory
Name:                   %{name}
Version:                %{version}
Release:                %{release}
License:                GPL
Group:                  Graphics
BuildRoot:              %{_tmppath}/%{name}-buildroot

%description
A package that simply manages the creation and ownership of
/usr/share/wallpapers, thus allowing multiple packages to put files
(presumably wallpaper files...) in that directory without having Requires
on unnecessary packages or encountering directory ownership issues.  All
such a package has to do is Require wallpaper-dir and those problems
are gone.

%prep

%build

%install
rm -rf $RPM_BUILD_ROOT
mkdir -p $RPM_BUILD_ROOT/%{_datadir}/wallpapers

%clean
rm -rf $RPM_BUILD_ROOT

%files
%defattr(-,root,root)
%dir %{_datadir}/wallpapers

%changelog
* Tue Aug 12 2003 Levi Ramsey <[EMAIL PROTECTED]> 1-1mdk
- First attempt... let's see if this works...

Reply via email to