Goswin von Brederlow wrote:
> Thomas Goirand writes:
>
>
>
> Srpm does have Build-Depends, right?
>
> MfG
> Goswin
>
>
Sure! It's called BuildRequires: in the spec files.
Thomas
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe".
Thomas Goirand writes:
> - Original message -
>> We were talking about dpkg-parsechangelog.
>>
>> MfG
>>Â Â Â Â Â Â Â Â Goswin
>
> Are you saying that dpkg-parsechangelog must also be available in RedHat like
> distros? Sorry, I didn't get it, but now I think you are quite right.
156 lines of twisted pre-processing bash code but it works. You can do
a strange merged deb/rpm structure as follows:
~/mypackagedir/distrospecificfilesdir
~/mypackagedir/SPECS
~/mypackagedir/SOURCES
~/mypackagedir/RPMS
etc for rpm.
~/mypackagedir/mypackagedir
~/mypackagedir/mypackagedir/DEBIAN
~/
- Original message -
> We were talking about dpkg-parsechangelog.
>
> MfG
> Goswin
Are you saying that dpkg-parsechangelog must also be available in RedHat like
distros? Sorry, I didn't get it, but now I think you are quite right.
Thomas
--
To UNSUBSCRIBE, email to debi
Thomas Goirand writes:
> Goswin von Brederlow wrote:
>> Then change that. :)
>>
>> We have rpm in Debian. Let them have dpkg.
>>
>> MfG
>> Goswin
>
> As much as I know, dpkg and debootstrap are both available as RPM
> packages for CentOS. But that doesn't mean you can use dpkg to instal
Goswin von Brederlow wrote:
> Then change that. :)
>
> We have rpm in Debian. Let them have dpkg.
>
> MfG
> Goswin
As much as I know, dpkg and debootstrap are both available as RPM
packages for CentOS. But that doesn't mean you can use dpkg to install
stuffs on your system. RPM and dpkg
Thomas Goirand writes:
> Russ Allbery wrote:
>
> Thomas Goirand writes:
>
>
>
> then in your debian/rules build rule, you can do something like:
>
>
>
>
> MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f1`
> MY_DEB_REL=`head
Russ Allbery wrote:
Thomas Goirand writes:
then in your debian/rules build rule, you can do something like:
MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
cut -d'-' -f1`
MY_DEB_REL=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')'
Thomas Goirand writes:
> then in your debian/rules build rule, you can do something like:
> MY_VERS=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f1`
> MY_DEB_REL=`head -n 1 debian/changelog | cut -d'(' -f2 | cut -d')' -f1 |
> cut -d'-' -f2`
> MY_PKGNAME=`head -n 1 d
Moving on.
As suggested I am simply going to have to hack/kludge rpm and deb with
a bunch of sed pre-processing of the respective spec, control and
postinst to make it work.
These two divergent schemes put a large burden of effort on developers
and documenters. Wish I could get deb and rpm folks
Ignacio Valdes wrote:
> So here is the use case, one that to my knowledge rpm or deb do not
> provide much guidance for and deb does not provide control fields for:
> Package is a vehicle for installing software that can create multiple
> instances. Further, those instances can be very long lived (
So here is the use case, one that to my knowledge rpm or deb do not
provide much guidance for and deb does not provide control fields for:
Package is a vehicle for installing software that can create multiple
instances. Further, those instances can be very long lived (decades)
and almost certainly
On Friday 30 April 2010 11:12:57 Ignacio Valdes wrote:
> So I am gathering that whereas it is repugnant to the dpkg design
> scheme to do it, but for the sake of rpm reconciliation the thread
> subject question: accessing control file values in postinst is not
> simple to do other than with major c
So I am gathering that whereas it is repugnant to the dpkg design
scheme to do it, but for the sake of rpm reconciliation the thread
subject question: accessing control file values in postinst is not
simple to do other than with major changes like sed pre-processing and
such?
Is that the situation
14 matches
Mail list logo
