Hi,

what dependency issue is this? AFAIK we should remove all
zypp/yum/satsolver packages from devel:tools:building as mic doesn't at
least require them when bootstrap mode is used which is the default mode. If this is just Requires: zypper in the mic2 package then that line should be removed from the package. As said before using --run-mode=0 which is default shouldn't require libzypp, libsatsolver or zypper to be installed on the host system.

Regards,
Marko

On 09/06/2011 03:27 PM, Zhang Qiang wrote:
Hi,
Adding new package zypper in project devel:tools:building. Please review and 
accept ASAP.

Justification for this new package:

fix dependenci issue in suse system

Thank You,
Zhang Qiang

[This message was auto-generated]

---

Request #23796:

   submit:   home:xiaoqiang:branches:devel:tools:building/zypper(r2)(cleanup) 
->  devel:tools:building/zypper


Message:
     fix dependenci issue in suse system

State:   new          2011-09-06T05:19:33 xiaoqiang
Comment: None


This is a NEW package in devel:tools:building project.
The files in the new package:
zypper/
   |__  0001-Support-searching-file-with-full-path.patch
   |__  0001-multi-ver-package-should-be-erased-from-notupdated-l.patch
   |__  0002-Support-fuzzy-search-file.patch
   |__  Makefile
   |__  zypper-1.6.10.tar.bz2
   |__  zypper-rpmlintrc
   |__  zypper.changes
   |__  zypper.spec
   |__  zypper.yaml

The content of the YAML file, zypper.yaml:
===================================================================
Name: zypper
Summary: Command line software manager using libzypp
Version: 1.6.10
Release: 1
Group: System/Packages
License: GPL v2 or later
URL: http://en.opensuse.org/Zypper
Sources:
     - "%{name}-%{version}.tar.bz2"
     - "%{name}-rpmlintrc"
Patches:
#    - 0001-multi-ver-package-should-be-erased-from-notupdated-l.patch
     - 0001-Support-searching-file-with-full-path.patch
     - 0002-Support-fuzzy-search-file.patch
Description: |
     Zypper is a command line tool for managing software. It can be used to add
     package repositories, search for packages, install, remove, or update 
packages,
     install patches, hardware drivers, verify dependencies, and more.

     Zypper can be used interactively or non-interactively by user, from 
scripts,
     or front-ends.
Requires:
     - procps
PkgConfigBR:
     - libzypp
     - augeas
PkgBR:
     - boost-devel>= 1.33.1
     - gettext-devel>= 0.15
     - readline-devel>= 5.1
     - cmake>= 2.4.6
     - gcc-c++>= 4.1
Builder: cmake
LocaleName: zypper
ConfigOptions:
     - -DCMAKE_INSTALL_PREFIX=/usr
     - -DSYSCONFDIR=%{_sysconfdir}
     - -DMANDIR=%{_mandir}
     - -DCMAKE_VERBOSE_MAKEFILE=TRUE
     - -DCMAKE_C_FLAGS_RELEASE:STRING="%{optflags}"
     - -DCMAKE_CXX_FLAGS_RELEASE:STRING="%{optflags}"
     - -DCMAKE_BUILD_TYPE=Release
     - -DUSE_TRANSLATION_SET=${TRANSLATION_SET:-zypper}

===================================================================


The content of the spec file, zypper.spec:
===================================================================
#
# Do NOT Edit the Auto-generated Part!
# Generated by: spectacle version 0.22
#
#>>  macros
#<<  macros

Name:       zypper
Summary:    Command line software manager using libzypp
Version:    1.6.10
Release:    1
Group:      System/Packages
License:    GPL v2 or later
URL:        http://en.opensuse.org/Zypper
Source0:    %{name}-%{version}.tar.bz2
Source1:    %{name}-rpmlintrc
Source100:  zypper.yaml
Patch0:     0001-Support-searching-file-with-full-path.patch
Patch1:     0002-Support-fuzzy-search-file.patch
Requires:   procps
BuildRequires:  libzypp-devel
BuildRequires:  pkgconfig(augeas)
BuildRequires:  boost-devel>= 1.33.1
BuildRequires:  gettext-devel>= 0.15
BuildRequires:  readline-devel>= 5.1
BuildRequires:  cmake>= 2.4.6
BuildRequires:  gcc-c++>= 4.1


%description
Zypper is a command line tool for managing software. It can be used to add
package repositories, search for packages, install, remove, or update packages,
install patches, hardware drivers, verify dependencies, and more.

Zypper can be used interactively or non-interactively by user, from scripts,
or front-ends.




%prep
%setup -q -n %{name}-%{version}

# 0001-Support-searching-file-with-full-path.patch
%patch0 -p1
# 0002-Support-fuzzy-search-file.patch
%patch1 -p1
#>>  setup
#<<  setup

%build
#>>  build pre
#<<  build pre

mkdir meego-build
cd meego-build
cmake ..  \
     -DCMAKE_INSTALL_PREFIX=/usr \
     -DSYSCONFDIR=%{_sysconfdir} \
     -DMANDIR=%{_mandir} \
     -DCMAKE_VERBOSE_MAKEFILE=TRUE \
     -DCMAKE_C_FLAGS_RELEASE:STRING="%{optflags}" \
     -DCMAKE_CXX_FLAGS_RELEASE:STRING="%{optflags}" \
     -DCMAKE_BUILD_TYPE=Release \
     -DUSE_TRANSLATION_SET=${TRANSLATION_SET:-zypper}

make %{?jobs:-j%jobs}

#>>  build post
make -C po %{?jobs:-j %jobs} translations
#<<  build post
%install
rm -rf %{buildroot}
#>>  install pre
#<<  install pre
cd meego-build
%make_install

#>>  install post
make -C po install DESTDIR=$RPM_BUILD_ROOT
# Create filelist with translations
cd ..
%{__install} -d -m755 %buildroot%_var/log
touch %buildroot%_var/log/zypper.log

#<<  install post
%find_lang zypper






%files -f zypper.lang
%defattr(-,root,root,-)
#>>  files
%config(noreplace) %{_sysconfdir}/zypp/zypper.conf
%config(noreplace) %{_sysconfdir}/logrotate.d/zypper.lr
%config(noreplace) %{_sysconfdir}/logrotate.d/zypp-refresh.lr
%{_sysconfdir}/bash_completion.d/zypper.sh
%{_bindir}/zypper
%{_bindir}/installation_sources
%{_sbindir}/zypp-refresh
%verify(not mode) %attr (755,root,root) %{_sbindir}/zypp-refresh-wrapper
%dir %_datadir/zypper
%_datadir/zypper/zypper.aug
%dir %_datadir/zypper/xml
%_datadir/zypper/xml/xmlout.rnc
%doc %{_mandir}/*/*
%doc %dir %{_datadir}/doc/packages/zypper
%doc %{_datadir}/doc/packages/zypper/TODO
%doc %{_datadir}/doc/packages/zypper/zypper-rug
%doc %{_datadir}/doc/packages/zypper/COPYING
%doc %{_datadir}/doc/packages/zypper/HACKING
# declare ownership of the log file but prevent
# it from being erased by rpm -e
%ghost %config(noreplace) %{_var}/log/zypper.log
#<<  files



===================================================================

_______________________________________________
MeeGo-commits mailing list
[email protected]
http://lists.meego.com/listinfo/meego-commits

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to