Hi!
Am 17.01.2012 02:55, schrieb Adam Borowski:
> Even binaries that don't have their sources in this package but are
> shipped somewhere else in Debian are ok.
Sorry, but written that way it is wrong.. Or at least could be
interpreted wrong. For _everything_ Debian ships in main we must have
t
On Tue, Jan 17, 2012 at 03:00:04AM +0200, Alexey Eromenko wrote:
> > Is the source being repackaged for DFSG reasons? If not, ‘~dfsg’ is a
> > confusing choice.
>
> VirtualBox src ships with binary *.exe, which are forbidden in Debian.
.exe file are fine, as long as they can be rebuilt with free
> Is the source being repackaged for DFSG reasons? If not, ‘~dfsg’ is a
> confusing choice.
VirtualBox src ships with binary *.exe, which are forbidden in Debian.
I don't know specific paragraphs of violations.
But I'm just a Debian-student, not mentor (@_@)
--
-Alexey Eromenko "Technologov"
Alexey Eromenko writes:
> Yes, you should replace inside sources, and call it ~dfsg.
Is the source being repackaged for DFSG reasons? If not, ‘~dfsg’ is a
confusing choice.
--
\ “Religious faith is the one species of human ignorance that |
`\ will not admit of even the *possibil
On Tue, Jan 17, 2012 at 8:28 AM, Alexey Eromenko wrote:
> Yes, you should replace inside sources, and call it ~dfsg.
In general it should be +dfsg not ~dfsg.
~dfsg/+dfsg should only be added when repacking for DFSG-related
reasons, so not in this case.
--
bye,
pabs
http://wiki.debian.org/Paul
2012/1/16 Björn Esser :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi there!
>
> How shall software be handled, when it needs
>
> - huge modifactions
Modify original sources in Debian.
> - scripts to be replaced by 'debianized' ones
> - to be extended by custom scripts or pr
2012/1/17 Björn Esser:
> - huge modifactions
Get those included upstream.
> - scripts to be replaced by 'debianized' ones
Make those scripts generic but configurable, send the required changes
upstream and drop in a second configuration file overriding the
defaults.
> - to be extended
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi there!
How shall software be handled, when it needs
- huge modifactions
- scripts to be replaced by 'debianized' ones
- to be extended by custom scripts or progs
when packaging it for debian?
Shall the custom / replaced stuff be pl
8 matches
Mail list logo