Eric Winger <[EMAIL PROTECTED]> writes:
> > That means (replace {dist} and {section} with sid,main or sid,local):
> >
> > repository/dists/{dist}/{section}/binary-<arch>/Package.gz
> > reposirory/pool/
> >
> Question: Since this is a local-use only repository, wouldn't it make
> more sense to give this a {dist} name that isn't linked with the
> current debian builds - sid, woody, etc. It's clear I can name the
> dist anything I want locally but current good practices should dictate
> what the name should be. Any recommendations?
As I said once you get outside users or have a stable/testing/unstable
mix yourself you will need backports. Having dist reflect the dist for
which the debs are compiled for served me well. The section and the
origin (in the release file) are enough for me.
At home I even have a /dists/sid/core/binary-arch/Packages.gz for a
stripped down repository for boot-floppies / debian-installer /
(c)debootstrap to install from.
> > You should also create Release files which you can mostly copy from
> > debian. Take care to change the Origin for BTS purposes though.
> >
> I haven't done this yet. Still getting my feet wet. But pinning is
> something I will look into.
It becomes important if you want to provide experimental packages that
shouldn't get installed unless requested. I had a patched mount here
and mldonkey. Not everyone that wanted mldonkey would want my mount.
Advanced stuff and for a strictly private repository overkill.
MfG (mit freundlichen Gruessen, with friendly greetings)
Goswin
PS: carefull with File://, apt-get source will create links into the
mirror and debuild will then erase the files from the repository and
replace them when you rebuild.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
