Bug 657412

I have read linked links and do not understand many things.
Draft guidelines have more questions then answers...

What particularly I should do with it file after place it in /lib/systemd/system/?

Should it be done only in rawhide?

"Should it be done only in rawhide?"

Yes, it's F15 feature.

"What particularly I should do with it file after place it in
/lib/systemd/system/?"


"Lennart Poettering 2010-08-11 09:50:56 EDT 

BTW, it is not sufficient to just drop the .service files into
/lib/systemd/system. It is also necessary to enable it when upgrading from an
old sysv-only rpm. How to implement that in the spec file with minimal work is
documented in daemon(7):

http://0pointer.de/public/systemd-man/daemon.html#id2562029"

https://bugzilla.redhat.com/show_bug.cgi?id=617324#c4

For upgrade you need to enable it, but I'm not sure what you need to do for install. AFAIR Lennart wrote something about not anabling services by default after installation.

Lennart, any comments?

See...

https://fedoraproject.org/wiki/Systemd_Packaging_Draft

As stated before I have read this document. Main question was - at least when planing finish it? Is there approximately date of meeting by it?

This service should start after network.target
After=syslog.target network.target

"Main question was - at least when
planing finish it? Is there approximately date of meeting by it?"

There is no any Fedora 15 feature for this (there is only https://fedoraproject.org/wiki/Features/systemd - but that does not include script conversion), but it would be nice provide this systemd service for F15.

I'm make such changes, please revisit scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2670327

But I still have some questions:
1) Is there new macros for path %{_libdir}/systemd/system/ ?
2) What I should do with old systemV service instructions like:
%preun                                                                                                                                                                  
# traditional SystemV service                                                                                                                                           
if [ $1 = 0 ]; then                                                                                                                                                     
   /sbin/service %{name} stop > /dev/null 2>&1                                                                                                                        
   /sbin/chkconfig --del %{name}                                                                                                                                      
fi
Now I leave it as is and only add systemd installation (and migration). Should it be deleted?

I installed this packege, and everything is running fine... but - it's my old version AFAICS.

[michal@dio ~]$ sudo systemctl status 3proxy.service
3proxy.service - 3proxy Proxy Server
	  Loaded: loaded (/lib/systemd/system/3proxy.service)
	  Active: active (running) since Tue, 21 Dec 2010 21:13:51 +0100; 4min 13s ago
	 Process: 8355 (/usr/bin/3proxy /etc/3proxy.cfg, code=exited, status=0/SUCCESS)
	Main PID: 8356 (3proxy)
	  CGroup: name=systemd:/system/3proxy.service
		  └ 8356 /usr/bin/3proxy /etc/3proxy.cfg

New version is installed to
/usr/lib64/systemd/system

You do not answer what do with legacy statements.

I did not answer because I do not know :)

I'm not a Fedora packager and frankly I know little about RPM's

(In reply to comment #7)
> I'm make such changes, please revisit scratch build:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2670327
> 
> But I still have some questions:
> 1) Is there new macros for path %{_libdir}/systemd/system/ ?
> 2) What I should do with old systemV service instructions like:
> %preun                                                                          
> # traditional SystemV service                                                   
> if [ $1 = 0 ]; then                                                             
>    /sbin/service %{name} stop > /dev/null 2>&1                                  
>    /sbin/chkconfig --del %{name}                                                
> fi
> Now I leave it as is and only add systemd installation (and migration). Should
> it be deleted?

I think those answers are given in the current policy draft:

https://fedoraproject.org/wiki/TomCallaway/Systemd_Revised_Draft

I think we should wait until it was accepted as guidelines, not draft only.

I think I now resolve it. Feedback welcome.

https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd
https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd
https://fedoraproject.org/wiki/Packaging:Tmpfiles.d