Re: Remove build-cruft from debian-edu src:package
- To: debian-edu@lists.debian.org
- Subject: Re: Remove build-cruft from debian-edu src:package
- From: Petter Reinholdtsen <pere@hungry.com>
- Date: Sun, 21 Sep 2014 15:33:55 +0200
- Message-id: <[🔎] 2fld2apqerg.fsf@diskless.uio.no>
- In-reply-to: <20140714105614.GA27529@an3as.eu>
- References: <20140709231454.Horde.lX__qWAJqdPd8AvZoRiIRw1@mail.das-netzwerkteam.de> <20140710080249.GD27599@ulrik.uio.no> <201407101108.45493.holger@layer-acht.org> <20140710092506.GE27599@ulrik.uio.no> <20140711085713.GA30573@an3as.eu> <20140713221849.Horde.PXoacqOTUQ_Kf38bPWrKAQ1@mail.das-netzwerkteam.de> <20140714105614.GA27529@an3as.eu>
[Andreas Tille]
>>>IMHO droping the two files is more error prone than keeping them.
>>>Confusion could be solved by documentation.
>>
>> So, I will keep those files (maybe under a slightly different name)
>> in Git and document why they exist there and continuously change
>> when there is an upload.
>
> Alternatively to a different name you might consider a different
> branch.
Btw, thanks to the heads up from Holger, I now understand where the
misunderstanding come from. In the debian-edu commit
25db0c5cd9c775c5a7e77a2416a5e47b92209299 dated 2008-04-05, you updated
the README to include:
Unpack this source package at any other place because the auto
generated debian/control file should not be checked into SVN.
We currently keep debian/control in VCS, and want to keep it in VCS, so
that part of the debian/README.source file should be changed to reflect
realities.
--
Happy hacking
Petter Reinholdtsen
Reply to: