I re-read my post and see it is turgid so I'll try and clarify. The
.deb that I am working from has for example in the un-built deb
layout:
%{debbuildroot}/etc/init.d/mystartshutdown.sh
%{debbuildroot}/etc/apache2/sites-enabled/mysite.conf
%{debbuildroot}/opt/myapplication/env
Deb seems to copy these into their respective sub-directories with no
extra code. For example: /etc/init.d/mystartshutdown.sh gets created
with dpkg -i thedeb.deb with no specific code doing this in any of the
deb control files.
I've built rpm's before so this seems to be more of a manual process
with rpm, hence my attempt at cp -Rf $whereRwe/etc /etc
Is there a more proper way of doing this with rpm?
-- IV
On Sun, Oct 4, 2009 at 5:04 PM, devzero2000 <pinto.elia@xxxxxxxxx> wrote:
> On Sun, Oct 4, 2009 at 6:52 AM, Ignacio Valdes <ivaldes@xxxxxxxxxx> wrote:
>>
>> Hi all again,
>>
>> I am going from a .deb to an rpm. The .deb has the files in
>> subdirectories such as /etc/init.d/foobar I planned to just have /etc
>> in the file list and then do a copy command such as:
>>
>> cp -Rf $whereRwe/etc /etc
>>
>> Is that the usual way you can deal with a deb-style file heirarchy
>> with rpm? Is there a better way?
>>
> It is not clear, at me almost, your question. BTW, the "deb-style file
> hierarchy" is almost equivalent to the files/directory you create in the rpm
> %install section, in the rpm buildroot. Now in %install section you can do
> something like this
>
> rm -rf %{buildroot}
> mkdir -p %{buildroot}/etc/init.d
> .......
> cp -a %{SOURCE1} %{buildroot}/etc/init.d/mypkg
> (where the (rpm) macro SOURCE1 was defined as
> Source1: mypkg.init for example in the SPEC)
> and in %files
>
> %files
> ........
>
> config(noreplace) /etc/init.d/myconfig
>
> So your question, IMHO, is not what deb does (deb is a packaging format e.g
> an ar archive with some metainfo for the dpkg , gdebi ecc. tools ) but what
> a dh_make does in building a skeleton for your package for make it a
> <pkg>.deb. Similar to what does, for example, for rpm the rpmdevtools (in
> particular rpmdev-newspec), with some difference of course. But there are
> other build system for rpm , as for deb.
>
> hth
>>
>> -- IV
>> _______________________________________________
>> Rpm-list mailing list
>> Rpm-list@xxxxxxxxxxxxx
>> http://lists.rpm.org/mailman/listinfo/rpm-list
>
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxxxxx
> http://lists.rpm.org/mailman/listinfo/rpm-list
>
>
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
