On Mon, Mar 10, 2014 at 10:50:07AM +, Wookey wrote:
+++ Thibaut Paumard [2014-03-10 10:59 +0100]:
Actually one way to go would be to upload the package without making the
split, downloading all the binaries, and comparing the files. This is
easier than manually building on porterboxes
Le 08/03/2014 14:02, Оlе Ѕtrеісhеr a écrit :
Hi,
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/. In the majority of
On Mon, Mar 10, 2014 at 10:19:29AM +0100, Thibaut Paumard wrote:
What I would try is to compile the package on two distinct architectures
(or more) and compare the result. That would work unless the build for
these files is non-deterministic or includes timestamps or information
on the build
On Sat, Mar 08, 2014 at 02:02:48PM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/.
Nothing
Thibaut Paumard thib...@debian.org writes:
Le 08/03/2014 14:02, Оlе Ѕtrеісhеr a écrit :
Hi,
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between
Andrey Rahmatullin w...@wrar.name writes:
On Sat, Mar 08, 2014 at 02:02:48PM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between
Hi,
Le 10/03/2014 10:45, Andrey Rahmatullin a écrit :
On Mon, Mar 10, 2014 at 10:19:29AM +0100, Thibaut Paumard wrote:
What I would try is to compile the package on two distinct architectures
(or more) and compare the result. That would work unless the build for
these files is
On Mon, Mar 10, 2014 at 10:54:44AM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/.
Hi,
Le 10/03/2014 10:50, Оlе Ѕtrеісhеr a écrit :
[packaging ESO MIDAS]
Let's see how far I come. BTW, Since I do not use it myself: Is it worth
to split it into core, applic, stdred, and contrib packages? Is there
any use for keeping the source?
It's already great to package it, don't overdo
Andrey Rahmatullin w...@wrar.name writes:
On Mon, Mar 10, 2014 at 10:54:44AM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split
+++ Thibaut Paumard [2014-03-10 10:59 +0100]:
Hi,
Le 10/03/2014 10:45, Andrey Rahmatullin a écrit :
On Mon, Mar 10, 2014 at 10:19:29AM +0100, Thibaut Paumard wrote:
What I would try is to compile the package on two distinct architectures
(or more) and compare the result. That would work
+++ Оlе Ѕtrеісhеr [2014-03-10 11:39 +0100]:
Andrey Rahmatullin w...@wrar.name writes:
On Mon, Mar 10, 2014 at 10:54:44AM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
On Mon, Mar 10, 2014 at 11:39:22AM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/.
Andrey Rahmatullin w...@wrar.name writes:
On Mon, Mar 10, 2014 at 11:39:22AM +0100, Оlе Ѕtrеісhеr wrote:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split
* Andrey Rahmatullin w...@wrar.name, 2014-03-10, 20:24:
FHS does: Miscellaneous architecture-independent
application-specific static files and subdirectories must be placed
in /usr/share. [1]
Do we enforce this?
Not really.
9.1.1 File System Structure
The location of all files and
On Mon, Mar 10, 2014 at 03:51:01PM +0100, Jakub Wilk wrote:
I also wonder if finding an arch-indep file in /usr/lib should
result in an RC bug.
No. We should relax the policy to match the current practice.
On Mon, Mar 10, 2014 at 03:40:33PM +0100, Оlе Ѕtrеісhеr wrote:
Since the Policy 9.1.1
Jakub Wilk jw...@debian.org writes:
* Andrey Rahmatullin w...@wrar.name, 2014-03-10, 20:24:
I also wonder if finding an arch-indep file in /usr/lib should result
in an RC bug.
No. We should relax the policy to match the current practice.
I concur -- I really doubt this is important enough
On Mon, Mar 10, 2014 at 1:44 PM, Russ Allbery r...@debian.org wrote:
Jakub Wilk jw...@debian.org writes:
* Andrey Rahmatullin w...@wrar.name, 2014-03-10, 20:24:
I also wonder if finding an arch-indep file in /usr/lib should result
in an RC bug.
No. We should relax the policy to match the
On Sat, Mar 08, 2014 at 08:47:41PM +0100, Оlе Ѕtrеісhеr wrote:
Bartosz Feński bart...@fenski.pl writes:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split
Osamu Aoki osamu_aoki_h...@nifty.com writes:
On Sat, Mar 08, 2014 at 08:47:41PM +0100, Оlе Ѕtrеісhеr wrote:
Bartosz Feński bart...@fenski.pl writes:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the
W dniu 09.03.2014 16:55, Оlе Ѕtrеісhеr pisze:
Osamu Aoki osamu_aoki_h...@nifty.com writes:
On Sat, Mar 08, 2014 at 08:47:41PM +0100, Оlе Ѕtrеісhеr wrote:
Bartosz Feński bart...@fenski.pl writes:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common
Bartosz Feński bart...@fenski.pl writes:
W dniu 09.03.2014 16:55, Оlе Ѕtrеісhеr pisze:
Osamu Aoki osamu_aoki_h...@nifty.com writes:
On Sat, Mar 08, 2014 at 08:47:41PM +0100, Оlе Ѕtrеісhеr wrote:
Bartosz Feński bart...@fenski.pl writes:
I am packaging some older software (eso-midas, [1]) that
Hi,
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/. In the majority of cases, this could be done
automatically by
W dniu 08.03.2014 14:02, Оlе Ѕtrеісhеr pisze:
Hi,
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/. In the majority of
Bartosz Feński bart...@fenski.pl writes:
I am packaging some older software (eso-midas, [1]) that installs
everything into a common directory (f.e. /usr/lib/eso-midas/). However,
the FHS requires that this should be split between /usr/share/ and
/usr/lib/arch/. In the majority of cases, this
25 matches
Mail list logo
