Debian Bug report logs - #647788
systemd: Please provide systemd.pc in a separate package

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Gergely Nagy <algernon@balabit.hu>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: systemd: Please provide systemd.pc in a separate package

Date: Sun, 06 Nov 2011 12:38:20 +0100

Package: systemd
Version: 37-1
Severity: wishlist

I'm working with a package that can be compiled with systemd support,
and my current version already makes use of libsystemd-daemon-dev, but
there's one remaining issue I have: if I want to automatically figure
out the systemdsystemunitdir, then I need the systemd.pc file, which is
currently in the systemd package.

While I can build-depend on systemd, that would be a bit of an overkill,
in my opinion. I can also hard-code the path (which is what I'm doing
now), but I don't like hard-coding stuff when there's a way to figure
out paths automatically at build time.

For this reason, I think it would be useful to move the systemd.pc file
to a separate package, perhaps to libsystemd-daemon-dev? Though, I might
be missing the obvious, and there's a good reason the file is where it
is, in which case, this report should be closed.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  initscripts         2.88dsf-13.13
ii  libacl1             2.2.51-4     
ii  libaudit0           1.7.18-1     
ii  libc6               2.13-21      
ii  libcap2             1:2.22-1     
ii  libcryptsetup1      2:1.3.0-3    
ii  libdbus-1-3         1.4.16-1     
ii  libpam0g            1.1.3-5      
ii  libselinux1         2.1.0-4      
ii  libsystemd-daemon0  37-1         
ii  libsystemd-login0   37-1         
ii  libudev0            172-1        
ii  libwrap0            7.6.q-21     
ii  udev                172-1        
ii  util-linux          2.19.1-5     

Versions of packages systemd recommends:
ii  libpam-systemd  37-1

Versions of packages systemd suggests:
ii  python       2.7.2-9
ii  systemd-gui  37-1   

-- no debconf information
-- 
|8]

Message #10 received at 647788-done@bugs.debian.org (full text, mbox, reply):

From: Tollef Fog Heen <tfheen@err.no>

To: Gergely Nagy <algernon@balabit.hu>

Cc: 647788-done@bugs.debian.org

Subject: Re: Bug#647788: systemd: Please provide systemd.pc in a separate package

Date: Sat, 30 Jun 2012 20:45:10 +0200

]] Gergely Nagy 

> While I can build-depend on systemd, that would be a bit of an overkill,
> in my opinion. I can also hard-code the path (which is what I'm doing
> now), but I don't like hard-coding stuff when there's a way to figure
> out paths automatically at build time.

Why would it be overkill?  It's a bit heavy for just a single file, but
a new package for a single file would be silly too, since it should then
go in systemd-dev.

As per your suggestion, I think I'm just going to close this as
wontfix. :-)

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Send a report that this bug log contains spam.